Hi all,

I've been doing some testing on my Synchronet 3.21 system under Linux, and I ran into something I'm not entirely sure I'm interpreting correctly. I wanted to run it by the group in case I'm misunderstanding expected behavior.

My setup is a fairly standard one where Synchronet starts as root (to bind to low ports) and then drops privileges to the sbbs user.

While troubleshooting an unrelated login delay, I noticed that after restarting the BBS using sudo, a couple of files ended up owned by root:

- /sbbs/data/msgs/0001.msg
- /sbbs/data/error.log

When those files are owned by root, logging in (especially as user #1) introduces a noticeable delay during the logon process. Once I change ownership back to sbbs:sbbs, the delay goes away immediately.

That made me wonder a couple things:

- Is it expected that these files might be created or touched before the privilege drop occurs?
- Or should they normally end up owned by the runtime user (sbbs) even after a restart?
- Is there a recommended way to avoid this situation when restarting (for example, a preferred service method)?

It's entirely possible I'm missing something about the startup sequence, so I figured I'd ask before digging further in the wrong direction.

Really appreciate any insight.

-Winzlo

� The Down-Lo BBS � bbs.winzlo.com
--- SBBSecho 3.37-Linux
* Origin: The Down-Lo BBS * bbs.winzlo.com (1:154/140)

Re: Question about file ownership after restart and possible login delay
By: Winzlo to All on Fri Apr 24 2026 08:58 am

Hi all,

I've been doing some testing on my Synchronet 3.21 system under Linux, and I ran into something I'm not entirely sure I'm interpreting correctly. I wanted to run it by the group in case I'm misunderstanding expected behavior.

My setup is a fairly standard one where Synchronet starts as root (to bind to low ports) and then drops privileges to the sbbs user.

While troubleshooting an unrelated login delay, I noticed that after restarting the BBS using sudo, a couple of files ended up owned by root:

- /sbbs/data/msgs/0001.msg
- /sbbs/data/error.log

When those files are owned by root, logging in (especially as user #1) introduces a noticeable delay during the logon process. Once I change ownership back to sbbs:sbbs, the delay goes away immediately.

That made me wonder a couple things:

- Is it expected that these files might be created or touched before the privilege drop occurs?
- Or should they normally end up owned by the runtime user (sbbs) even after a restart?
- Is there a recommended way to avoid this situation when restarting (for example, a preferred service method)?

It's entirely possible I'm missing something about the startup sequence, so I figured I'd ask before digging further in the wrong direction.

Really appreciate any insight.

I don't recommend running sbbs under sudo. Fix the file ownerships and use the setcap target instead (see https://wiki.synchro.net/howto:linux_non-root for details) and run as the 'sbbs' (or equivalent user) - never root.
--
digital man (rob)

This Is Spinal Tap quote #22:
David St. Hubbins: Here lies David St. Hubbins... and why not?
Norco, CA WX: 66.3�F, 58.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Winzlo wrote to All <=-

Hi all,

I've been doing some testing on my Synchronet 3.21 system under Linux,
and I ran into something I'm not entirely sure I'm interpreting
correctly. I wanted to run it by the group in case I'm misunderstanding expected behavior.

My setup is a fairly standard one where Synchronet starts as root (to
bind to low ports) and then drops privileges to the sbbs user.

While troubleshooting an unrelated login delay, I noticed that after restarting the BBS using sudo, a couple of files ended up owned by
root:

- /sbbs/data/msgs/0001.msg
- /sbbs/data/error.log

When those files are owned by root, logging in (especially as user #1) introduces a noticeable delay during the logon process. Once I change ownership back to sbbs:sbbs, the delay goes away immediately.

<SNIP>

Go to the Wiki and search the term 'setcap'. You don't need to be
starting the system as root.




... Users come in two types: Those who have lost data, and those who will.
--- MultiMail/Linux v0.52
� Synchronet � Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Question about file ownership after restart and possible login delay
By: Gamgee to Winzlo on Fri Apr 24 2026 12:47 pm

Go to the Wiki and search the term 'setcap'. You don't need to be
starting the system as root.

Did the trick. Thanks DM.

-Winzlo

� The Down-Lo BBS � bbs.winzlo.com
--- SBBSecho 3.37-Linux
* Origin: The Down-Lo BBS * bbs.winzlo.com (1:154/140)

Winzlo wrote to Digital Man <=-

Re: Question about file ownership after restart and possible login
By: Gamgee to Winzlo on Fri Apr 24 2026 12:47 pm

Go to the Wiki and search the term 'setcap'. You don't need to be
starting the system as root.

Did the trick. Thanks DM.

Well, it was me that said that, but OK. ;-)



... The Bagginses, they steals our taglines, preciousss...
--- MultiMail/Linux v0.52
� Synchronet � Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Question about file ownership after restart and possible login delay
By: Gamgee to Winzlo on Fri Apr 24 2026 09:34 pm

Well, it was me that said that, but OK. ;-)

Ok, and that one was my bad. Apologies and respect. given.

-Winzlo

� The Down-Lo BBS � bbs.winzlo.com

---
� Synchronet � The Down-Lo BBS * bbs.winzlo.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)