Subj : Re: For you SBBS Sysops o
To   : Gamgee
From : Nightfox
Date : Sat Jun 29 2024 04:42 pm

  Re: Re: For you SBBS Sysops o
  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.

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

Nightfox

---
 þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

.