Using pidof to check if there is already a monotone running causes a problem if tracmtn is used and trac is loaded before monotone and gets a request because it forks a mtn client on the server. This causes the monotone init.d script to think that the daemon is already running and it doesnt fork it. Checking if the mtn that is running belongs to the user that it is told to fork as should be enough to overcome this problem but i dont know enough shell scripting to submit a patch for it. Reproducible: Always
--pid-file <arg> record process id of server is supported by the mtn serve command
(In reply to comment #0) > Using pidof to check if there is already a monotone running causes a problem Looking at dev-util/monotone/files/monotone.initd I can't see a pidof usage. It uses --pid-file= in the start function and stop uses the pidfile too. Can the trac instigation pass its own pid-file arguement to avoid conflict?
old init file was in use, no more issues
