On Thu Nov 26 00:25:40 +0100 2009, Serafeim Zanikolas wrote: > On Wed, Nov 25, 2009 at 05:24:33PM +0100, Andreas Bolka wrote: > > On Wed Nov 25 01:28:05 +0100 2009, Keith Rarick wrote: > > > What is the right thing to do? > > > > +1 for /usr/bin. > > > > Unless beanstalkd ever gains multi-user facilities, putting it in > > /usr/sbin is basically wrong, as it simply is no system binary and is > > _not_ intended to be used as system-wide service daemon. > > The upstream tarball comes with a sysv init script that assumes that there is > a single instance per host (it uses a lock file).
Ah, I forgot about the init script. > Whether a beanstalkd instance is used system-wide is a matter of > choice. I guess it then boils down to how you are about to package beanstalkd and for what target audience. If the package intends to mainly install beanstalkd as a system service (maybe with a sane default to listen only on the local interface), then /usr/sbin is certainly the correct place for the binary. If the package is intended to quickly make the binary and manpage available to discerning developers, then go with /usr/bin. -- Andreas -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
