Subj : Re: For you SBBS Sysops o
To   : Nightfox
From : Gamgee
Date : Sat Jun 29 2024 20:19:00

-=> Nightfox wrote to Gamgee <=-

 Ni>   Re: Re: For you SBBS Sysops o
 Ni>   By: Gamgee to Accession on Sat Jun 29 2024 01:14 pm

 Ac>> Not sure what you have against systemd. I gladly switched over when it

 Ga> I guess it's mostly the (assumed) philosophy that "let us manage all your
 Ga> startup processes the way we think is best, and you don't worry about the
 Ga> details".  I know that isn't quite accurate, because you can of course
 Ga> tweak systemd like most anything else, but that's as close as I can come
 Ga> to a reason.  I like to know exactly what's happening and have as much
 Ga> control over that as I can.  Another claim is that systemd does things "in
 Ga> parallel all at once" and thereby reduces boot time.  I don't care one
 Ga> little bit about that, as I don't reboot often and don't care if it takes
 Ga> 12 seconds, or 14 seconds.

 Ni> How do you normally run Synchronet on your system?  When I moved my BBS
 Ni> from Windows to Linux a couple years ago, for a little while I was just
 Ni> directly running sbbs from a command prompt, but I later set it up to
 Ni> run with systemd. I think one of the advantages of the systemd setup is
 Ni> it runs in the background, and I think I wouldn't even have to log in
 Ni> for it to be running. Also, systemd can monitor and restart processes
 Ni> that have crashed.  On Windows, every so often I saw Synchronet crash,
 Ni> seemingly randomly, and at one point when doing some debugging, it
 Ni> looked to me like the crash was caused by something in the Mozilla
 Ni> JavaScript library.  I didn't bother to debug further (I'd probably
 Ni> have to compile the JS libraries in debug mode), but I was using
 Ni> something for Windows that would monitor whether Synchronet was running
 Ni> and re-start it if it wasn't.  I feel like it's good that that feature
 Ni> is built-in with systemd.

I just run it from a terminal window while in the /sbbs/exec directory, 
with './sbbs syslog' .  I have several other terminals open tailing 
several logs, and another terminal for checking on things like 
backlogged mail or system load, etc.

I do not want it starting automatically when the computer is booted up, 
because perhaps I'm going to do something with the computer such as 
OS/security updates, or BBS updates, or tweaking of some kind; before 
the BBS starts.  When I'm ready for it to come up, I bring it up.  Doesn't
take much effort or time.  That way I also get to see that it did indeed
start properly, ports are opened/listening, etc.  I like to pay attention
to the small details to make sure all is running smoothly.


.... She sells unix shells by the sea shore.
--- MultiMail/Linux v0.52
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

.