I'm   using Smail3.1.29.1  #29.37 from the  debian
package  install, and having nothing but problems.
Ignoring the earlier file locking trouble, I'm now
discovering that for  some reason,  the  following
occurs:

        /USR/SBIN/CRON is spawned
        runq is called
        runq goes zombie
        cron goes zombie

The crontab for mail looks normal:

        03,23,43 * * * * /usr/bin/runq

This rinses, lathers and repeats until the machine
is crippled. Another oddity is that calling 'runq'
outside of cron  results in the creation of  /two/
runq processes. Anyone come across this behaviour?

   - Eamon Daly

Reply via email to