stderr.txt behaviour

Forums › Problems and Bug Reports

tullio
tullio
Joined: 22 Jan 05
Posts: 2118
Credit: 61407735
RAC: 0
5 Dec 2006 19:50:31 UTC
Topic 192158
(moderation:
    )

    I am running BOINC 5.6.4 on SuSE Linux 10.1. If I start the BOINC manager without starting first the client, the stderr.txt file remains empty in Einstein@home, while it gets recorded both in SETI@home and QMC@home. On the other hand, if I start the graphic window in QMC@home the stderr.txt file grows hugely with error messages and the run aborts after exausting a disk space of 10 GB. Has anybody recorded such a strange behaviour?
    Tullio

    PovAddict
    PovAddict
    Joined: 31 Mar 05
    Posts: 45
    Credit: 2508915
    RAC: 0

    stderr.txt behaviour

    7 Dec 2006 16:58:26 UTC
    Message 55838
    (moderation:
      )

      Quote:
      I am running BOINC 5.6.4 on SuSE Linux 10.1. If I start the BOINC manager without starting first the client, the stderr.txt file remains empty in Einstein@home, while it gets recorded both in SETI@home and QMC@home. On the other hand, if I start the graphic window in QMC@home the stderr.txt file grows hugely with error messages and the run aborts after exausting a disk space of 10 GB. Has anybody recorded such a strange behaviour?
      Tullio


      The latter problem seems to be a bug on QMC application...

      Comment viewing options

      Select your preferred way to display the comments and click "Save settings" to activate your changes.

      Forums › Problems and Bug Reports