Hi, and thanks for your quick reply, On 03/12/2012 10:45 PM, Simon MacMullen wrote: > The version of rabbitmq-server in Debian (2.6.1) is slightly out of date > as it lost its maintainer for a bit. The bug you reference should be > fixed in 2.7.0 / 2.7.1 (deb available from > http://www.rabbitmq.com/install-debian.html) due to the "rabbitmqctl > stop" command not returning until the server is actually stopped. > > The next release (2.8.0, imminent, by which time we should have a Debian > Maintainer on the RabbitMQ team to upload it) will switch to using > start-stop-daemon.
If you need somebody to act as upload sponsor, let me know, I can help (however, I don't want to become a permanent sponsor). > Finally, I'll look into not invoking userdel. That sounds plausible. A > quick google points me to Debian bug 621833, which seems to say "do not > remove". There's nothing written in the stone of the Debian policy for this, and in fact, it's quite a controversial topic. One thing is that if you do call userdel, you have to be extremely careful that absolutely no file are left on the hard drive with the UID/GID of the user you created. If you decide to just leave the system user, that's the easy path, and nobody will be able complain about it (it's a common way to do things, and it's the way maintainers do in RedHat/Fedora as well I believe). Cheers, Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
