On Oct 25, 2007 at 5:01 PM, Tomasz Sterna wrote: > Dnia 25-10-2007, Cz o godzinie 08:27 -0700, Mark Doliner pisze: > > 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'? > > ./configure --prefix=somedir HAVE to move the whole installation to > 'somedir'. > So we simply cannot use fixed paths. They HAVE to incorporate $(prefix).
For binaries and documentation I totally agree, but does it make sense to do that for files created at run time? > Ant this is the reason for this 'strange' paths. They are relative to > prefix - by default set to /usr/local, which is a place to software > specific to local installation (remember that in big Unix > installations /usr is NFS read-only mounted from shared storage for easy > system upgrades). Isn't that MORE of a reason to put the pid files in /var/run? If /usr is read-only and jabberd tries to write a pid file to /usr/var/run it would fail. The FHS even says, "/usr is shareable, read-only data. That means that /usr should be shareable between various FHS-compliant hosts and must not be written to. Any information that is host-specific or varies with time is stored elsewhere." (http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY) -Mark _______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
