Subj : Re: Synchronet for FreeBS
To   : alt.bbs.synchronet
From : Christine
Date : Wed Aug 10 2005 05:02 pm

From Newsgroup: alt.bbs.synchronet

Deuce wrote:
> To: Digital Man
>   Re: Re: Synchronet for FreeBS
>   By: Digital Man to Frank Reid on Wed Aug 10 2005 14:41:00
>
>  >  > Well, I figured out what's happening, but not why.  The pid listed =
in
>  >  > synchronet.pid is not actually the pid of the running process.
>  >
>  > It's probably the PID of the original thread (before forking). When sb=
bs for
>  > to run as daemon, it creates the file /var/run/sbbs.pid with the corre=
ct PID
>  > it for monitoring/controlling the process and all the child threads.
>
> Actually, what I think is more likely is that the process switches to the
> specified uid/gid *before* creating/updating the pid file.  What this mea=
ns is
> that you probobly ran sbbs as root once which created /var/run/sbbs.pid o=
wned
> as root with 0600 permissions... sbbs simply cannot update that pid file =
at
> all.
>
> The user sbbs is running as needs to have write access to the sbbs.pid fi=
le in
> order to update the file correct... and write access to /var/run (or what=
ever)
> to create a new file.
>
> Simply doing a chown on the existing sbbs.pid file should fix you up.
>
> ---
>  =FE Synchronet =FE ``Penguins make tasty snacks''
> --- Synchronet 3.12b-Win32 NewsLink 1.83
>  *  Vertrauen - Anaheim Hills, California - telnet://vert.synchro.net


Digital Man was right, my script wasn't using the sbbs.pid file, it was
capturing the pid on it's own, using ps and an unpleasant mixture of
commands. (grins)  This of course, was because I only run sbbs as
non-root, and the sbbs.pid thus never got created... so I didn't
realize it existed... now the script just uses sbbs.pid, because I'm
more than happy to let Synchronet do the work of making the pid file :)

--- Synchronet 3.12b-Win32 NewsLink 1.83

.