On 3/31/24 14:32, Alexandru N. Barloiu wrote:
I think in the past, the service file had a -v. Somewhere near the
present, they reverted to a non -v service file. So if you keep
upgrading distcc, prolly the service file still has a -v from past
installations. If you uninstall it, and install it again, then prolly
you got the new service file which is without -v. That prolly explains
why some machines still have it, and some don't.
On 4/1/2024 12:03 AM, Daniel Frey wrote:
On 3/31/24 13:59, Alexandru N. Barloiu wrote:
think the distcc.service file has an extra -v (--verbose). if you
remove that, it will behave as expected.
I checked all the units on one of the machines still showing the
problem and an extra '-v' is not present in any of the files.
That's a good thought though. I wouldn't have even thought about that
when I was looking at the unit files initially.
Dan
I did check, there's no '-v' in ps output. The systemd installations
were all new - they were converted from openrc.
276 ? SN 0:00 /usr/bin/distccd --no-detach --daemon
--port 3632 -N 15 --allow 127.0.0.1
277 ? SN 0:00 /usr/bin/distccd --no-detach --daemon
--port 3632 -N 15 --allow 127.0.0.1
278 ? SN 0:00 /usr/bin/distccd --no-detach --daemon
--port 3632 -N 15 --allow 127.0.0.1
279 ? SN 0:00 /usr/bin/distccd --no-detach --daemon
--port 3632 -N 15 --allow 127.0.0.1
I don't think it has anything to do with upgrading systemd as it was
installed fresh - I also replicated the issue after using an openrc
machine to switch to merged-usr (no systemd on it.)
Dan
