Thomas Klausner writes: > Hi! > Hello Thomas,
> I wanted to run a python service using an rc.d script. It knows to write a > pid file, but that is not good enough for our rc.d system. It complains: > > # /etc/rc.d/syncserver stop > > syncserver not running? (check /home/wiz/Projects/syncserver/syncserver.pid). > > I think this happens because the executable is not called “syncserver” but is > started using a python2.7 binary. So I tried setting > > command_interpreter="/home/wiz/Projects/syncserver/local/bin/python2.7" > > but then I got > > /etc/rc.d/syncserver: WARNING: $command_interpreter > /home/wiz/Projects/syncserver/local/bin/python2.7 != /bin/sh > > Is there a way to get python programs running nicely with rc.d and pid > support (i.e. “status” and “stop” support)? > [...] Was `command' adjusted too to the path of the script? Can you please share the possible problematic rc.d script? pkgsrc/chat/miniircd/files/miniircd.sh is a possible example (but it doesn't use any pidfile).