Eddy, > I'm using amavisd-new 2.6.1 and it's working pretty well. > On RedHat, when doing "# service amavisd stop", > the following error message appears in my logs and amavisd-new > refuse to stop > > amavis[11902]: Ignoring stale PID file /var/amavis/amavisd.pid, older > than system uptime 2 19:27:00 > > -rw-r----- 1 amavis amavis 0 Sep 25 08:07 amavisd.lock > -rw-r----- 1 amavis amavis 5 Sep 22 12:38 amavisd.pid > srwxr-x--- 1 amavis amavis 0 Sep 22 12:38 amavisd.sock
Which of the above is incorrect? Was the system uptime longer than 2.8 days, or was amavisd started later than Sep 22 12:38 but its .pid and .sock files were not created or were created somewhere else? Or maybe amavisd was not running at all when you tried to stop it? > But, it works correctly if I type the following commands > # touch /var/amavis/amavisd.pid > # service amavisd stop Is the information (process id) in the amavisd.pid correct and corresponds to the actually running master amavisd process? > Am I the only one with that problem ? So far I haven't heard of it. There was another problem reported recently regarding the kill(0) failing on restart (which will be fixed in 2.6.2), but this does not apply to your case. Mark ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
