Support Forum

Correct. When I wrote that script, I used start-stop-daemon (the standard process manager for services in Gentoo, probably other Linuxes as well). I start SABnzbd with the --pid argument, which creates the appropriate file in /var/run/sabnzbd/ so I don't have to know the PID directly. I believe that...

I submitted a working ebuild script with init and configuration files to the Gentoo bugzilla here . It works nicely for my use case, which is a single SAB instance. I don't use any sed/awk trickery when starting or stopping the process via start-stop-daemon, and the sabnzbd-[port#].pid file contains...

shypike wrote: You're going to get it in 0.6.1
--pid

Great news, shypike! Thank you. I'll submit the package to gentoo's bugzilla and try to have it included in the official tree.

shypike wrote: We'll see.
If it's not too complex it might get implemented.
Don't expect to much fanciness, like support in the UI.

Thank you for looking into it, shypike.  I prefer the command line anyway, so an obscure switch would be great for me.  No need to bring the GUI into it

You're right, port.pid would be a unique solution, since it wouldn't make any sense to run multiple SAB instances on the same port.

If this request is too obscure, I'll cook up my own solution using some shell scripting instead.  Cheers!

shypike: If you don't want to use an exit code for a PID, that's reasonable.  /var/run is certainly only writable by root, but packages can install their own subdirectories to play in, with appropriate permissions.  For instance, my tomcat webserver has a /var/run/tomcat-6 directory, owned by tomcat...

My apologies for bumping the old post, but it's unresolved and highly relevant to me. I'm working on an init script for Gentoo Linux using SABnzbd 0.6.0, and I'd like to have a way to launch SAB and get a PID back.  I notice that you get the pid using os.fork() in SABnzbd.py, but it's not returned o...