Summary: | mail-mta/exim-4.80.1: pidfile in /var/run - should be in /run | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcel Pennewiß <gentoo> |
Component: | [OLD] Server | Assignee: | Fabian Groffen <grobian> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, bertrand, net-mail+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcel Pennewiß
2013-02-03 21:19:34 UTC
Possible fix: * fix init-script * add "-oP /run/exim.pid" to conf.d/exim Shouldn't you have a /var/run -> /run symlink on your system? /me confused (In reply to comment #0) > Exim put pid-file to /var/run by default and init-script tries to use this > pid. Instead of /var/run /run should be used for pid-files. (my newly > installed system has no /var/run ;)) I also had such a problem with my own catalyst builds. But it was rather long ago and since then this problem was fixed somewhere. Currently all official stage3 builds have /var/run -> /run symlink. (In reply to comment #2) > Shouldn't you have a /var/run -> /run symlink on your system? > Of course this symlink should be present on the system. But AFAIK /run will be a part of FHS 3.0 and a lot of ebuilds use it already. So why not migrate? :) this is in 4.80.1-r1 Init-Script already uses /var/run instead of run. backup2 / # /etc/init.d/exim restart * Stopping exim ... * start-stop-daemon: fopen `/var/run/exim.pid': No such file or directory [ ok ] * Starting exim ... backup2 run # ls -l /run/exim.pid -rw-r--r-- 1 root mail 6 5. Okt 10:54 /run/exim.pid Ah, fixed init.d script now too. In 4.80.1-r3 and 4.82 |