Results 1 to 4 of 4

Thread: Error in Client

  1. 12-11-2002, 02:12 AM #1
    Pascal
    Pascal is offline
    Senior Member
    Join Date
    Apr 2002
    Location
    Near Frankfurt, Germany
    Posts
    106
    Send a message via ICQ to Pascal Send a message via MSN to Pascal Send a message via Yahoo to Pascal

    Angry Error in Client

    As I saw that morning in the client folder,
    I saw this in the really huge error.log (greater than 1 megabyte)

    Code:
     !!! Contact between residues ARG       and TRP        too close !!!
 !!! Contact between residues SER       and SER        too close !!!
 !!! Contact between residues CYS       and ALA        too close !!!
 !!! Contact between residues VAL       and GLY        too close !!!
 !!! Contact between residues ARG       and LEU        too close !!!
 !!! Contact between residues ALA       and ASN        too close !!!
 !!! Contact between residues SER       and ALA        too close !!!
 !!! Contact between residues ALA       and SER        too close !!!
 !!! Contact between residues ASN       and VAL        too close !!!
 !!! Contact between residues ASN       and GLN        too close !!!
 !!! Contact between residues GLN       and THR        too close !!!
 !!! Contact between residues ARG       and ALA        too close !!!
 !!! Contact between residues SER       and THR        too close !!!
 !!! Contact between residues ARG       and ALA        too close !!!
 !!! Contact between residues CYS       and GLY        too close !!!
 !!! Contact between residues ASN       and TYR        too close !!!
    I'm using the linux icc client, someone else has also detected this error.
    Science-at-home.de
    Reply With Quote Reply With Quote
  2. 12-11-2002, 05:46 AM #2
    Michael H.W. Weber
    Michael H.W. Weber is offline
    Senior Member Michael H.W. Weber's Avatar
    Join Date
    Apr 2002
    Location
    Germany
    Posts
    147
    Is there a simple switch to disable error.log generation?

    I care less about the rapidly increasing file size but this continuous harddisk access drives me nuts - at least in the long run. I also don't think it does much good regarding my drive's lifetime.

    Michael.

    P.S.: RAM disk no option.
    http://www.rechenkraft.net - Germany's largest distributed computing community

    - - - - - - - - - -
    RNAs are nanomachines or nanomachine building blocks. Examples: The ribosome, RNase P, the cellular protein secretion machinery and the spliceosome.
    Reply With Quote Reply With Quote
  3. 12-11-2002, 10:59 AM #3
    Brian the Fist
    Brian the Fist is offline
    Moderator Brian the Fist's Avatar
    Join Date
    Mar 2002
    Location
    Toronto, Canada
    Posts
    1,558
    see www.distributedfolding.org/news.html
    Howard Feldman
    Reply With Quote Reply With Quote
  4. 12-11-2002, 01:56 PM #4
    bwkaz
    bwkaz is offline
    Senior Member
    Join Date
    Mar 2002
    Location
    MI, U.S.
    Posts
    697
    Originally posted by Michael H.W. Weber
    Is there a simple switch to disable error.log generation?
    Of course there is. There were actually a couple posted in the other thread -- the one I liked was ln -sf /dev/null error.log, but that doesn't work on M$ OS'es (the less-than-intelligent filesystem lacks symlink (or indeed, hard link as well) capability). You can also create a directory named error.log, and hopefully that will also stop it...

    (I realize that these aren't switches, of course...)
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules