Re: [gentoo-user] Re: silencing distcc with systemd
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
Re: [gentoo-user] Re: silencing distcc with systemd
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
Re: [gentoo-user] Re: silencing distcc with systemd
/etc/systemd/system/distccd.service.d/00gentoo.conf or the service file. has to be. there cant be anything else. that's how distcc behaves when started with -v. do a ps axw. figure out where the -v is coming from. maybe a systemctl daemon-reload && systemctl restart distccd. cant be anything else but a -v 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
Re: [gentoo-user] Re: silencing distcc with systemd
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
Re: [gentoo-user] Re: silencing distcc with systemd
think the distcc.service file has an extra -v (--verbose). if you remove that, it will behave as expected. On 3/31/2024 11:57 PM, Daniel Frey wrote: On 3/29/24 22:38, Daniel Frey wrote: Hi all, I've moved a couple of machines from openrc to systemd. I have discovered this odd problem. On openrc, distcc was quiet during building packages. It would obey environment variable set in /etc/env.d: DISTCC_DIR=/var/distcc DISTCC_ENABLE_DISCREPANCY_EMAIL= DISTCC_FALLBACK=1 DISTCC_SAVE_TEMPS=0 DISTCC_SSH= DISTCC_TCP_CORK= DISTCC_VERBOSE=0 This currently shows up in the enviroment (checked with `set`.) * snipped the rest * Just an update. I have figured out it isn't systemd causing this issue. I did upgrade several machines. 1. Upgraded the system profile. 2. Converted from split-usr to merged-usr. 3. Converted to systemd. It turns out step 2 caused the problem. I don't know why, but it does - I tested this by converting an openrc machine that I hadn't upgraded yet from split-usr to merged-usr and the problem presented itself (no system on that machine yet.) I did notice the machine I completely reinstalled from scratch (using systemd from the start) did not show signs of this issue. I reinstalled the other distcc host using systemd from the start, installed and configured distcc and it all works as expected. Now to reinstall the slower Celeron devices... come to think of it, I initially installed them in 2011. They haven't ever been reinstalled. Just repurposed. Dan
[gentoo-user] Re: silencing distcc with systemd
On 3/29/24 22:38, Daniel Frey wrote: Hi all, I've moved a couple of machines from openrc to systemd. I have discovered this odd problem. On openrc, distcc was quiet during building packages. It would obey environment variable set in /etc/env.d: DISTCC_DIR=/var/distcc DISTCC_ENABLE_DISCREPANCY_EMAIL= DISTCC_FALLBACK=1 DISTCC_SAVE_TEMPS=0 DISTCC_SSH= DISTCC_TCP_CORK= DISTCC_VERBOSE=0 This currently shows up in the enviroment (checked with `set`.) * snipped the rest * Just an update. I have figured out it isn't systemd causing this issue. I did upgrade several machines. 1. Upgraded the system profile. 2. Converted from split-usr to merged-usr. 3. Converted to systemd. It turns out step 2 caused the problem. I don't know why, but it does - I tested this by converting an openrc machine that I hadn't upgraded yet from split-usr to merged-usr and the problem presented itself (no system on that machine yet.) I did notice the machine I completely reinstalled from scratch (using systemd from the start) did not show signs of this issue. I reinstalled the other distcc host using systemd from the start, installed and configured distcc and it all works as expected. Now to reinstall the slower Celeron devices... come to think of it, I initially installed them in 2011. They haven't ever been reinstalled. Just repurposed. Dan
