By default jabberd 2 uses '@localstatedir@/jabberd/pid/component.pid' as the
pid file for each component. This ends up being
'/usr/local/var/jabberd/pid/c2s.pid' for me when I don't specify a prefix.
This seems weird to me. I don't even have a /usr/var or /usr/local/var on
Ubuntu Linux or CentOS Linux, and I can't find any reference to it in the
Filesystem Hierachy Standard (FHX), so I don't understand why autoconf sets
localstatedir to be '${prefix}/var/' in the first place. The FHS suggests that
pid files be placed under /var/run/
(http://www.pathname.com/fhs/pub/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA).
Two possible improvements to this path:
1. @localstatedir@/run/jabberd/component.pid
2. /var/run/jabberd/component.pid
I realize that not all operating systems follow the FHS, but it seems like
either of these alternatives would at least be an improvement. What do other
people think?
Similarly, how do people feel about changing the default log file from
'@localstatedir@/jabberd/log/component.log' to '/var/log/jabberd/component.log'?
-Mark
_______________________________________________
Jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
