what could be the problem with a system that regularly puts quite a number of processes into "uninterruptible sleep" (according to top) for some minutes, and then releases them after a that (long) while? for instance, logging in to courierpop3d through port 110 allows me to enter user and password according to the POP3 protocol, but then courierpop3d goes into uninterruptible sleep for several minutes before acknowledging the successful authentication in the POP3 dialog. even a simple /bin/ls invocation gets put into 'D' status occassionally and will only return from that sleep after minutes of occupying the console (not reacting to SIGINT or SIGSUSP). the logs show nothing, and i can't access the machine physically to check if the hardware is acting up.
i would appreciate any hints. this is a vital system and i am sweating about it. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck the only real advantage to punk music is that nobody can whistle it.
msg03787/pgp00000.pgp
Description: PGP signature
