Serafeim Zanikolas is packaging beanstalkd for Debian, and he's suggested that beanstalkd should go in sbin, because it's a system program rather than an end-user program. I tend to think of beanstalkd as an end-user program.
With his permission, I'm forwarding our conversation here. Sreafeim Zanikolas wrote: > > > binary in /usr/sbin (not /usr/bin) as it's a system program. > > > > That's an interesting point. I've never thought of beanstalkd as a > > system program. Although it's a daemon, it isn't part of the OS. It is > > a tool that people use to help them build applications. > > > > It would be essentially impossible to run beanstalkd as a system > > service shared between all users -- they would wind up stepping all > > over each other. Usually, each user runs her own instance of > > beanstalkd. > > > > But I haven't actually thought about this very much. With a good > > argument I could be persuaded otherwise. > > According to the FHS, /usr/bin is for user commands whereas /usr/sbin for > system commands. IMHO any deamon (that's not related to desktop or end user > stuff) is clearly a system command. But maybe that's just me :) What is the right thing to do? kr -- 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.
