I think you are right, it should ideally be done after switching the user. In practice, I think few people will actually encounter the problematic situation.
Unfortunately, fixing it now would cause this problem, once, for almost everyone. Any ideas about how to do the transition smoothly? kr On Sun, Feb 21, 2010 at 11:16 PM, Jeremy Hinegardner <[email protected]> wrote: > Hi, > > Just had a thought, shouldn't the binlog lock file be opened and locked > AFTER the user is switched? > > If beanstalk is started with an init script, and using the -u option to > su to another user, then it is started as root, and the lockfile for > the binlog is owned by root with 0600 permissions. > > This means that for a beanstalkd server started once as root with the > -u option to su to a user and then shutdown. The only way to have > a beanstalkd server started again with that particular binlog is to > start it as root, or manually make change/erase the lock file so that > some other user may start the service. > > is this an issue? > > enjoy, > > -jeremy > > -- > ======================================================================== > Jeremy Hinegardner [email protected] > > -- > 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. > > -- 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.
