Re: [systemd-devel] nfs-convert.service

2022-08-22 Thread Lennart Poettering
On Fr, 19.08.22 11:21, Steve Dickson (ste...@redhat.com) wrote: > Hello, > > I'm trying to remove nfsconvert from Fedora but I'm > getting the following systemd error after I removed > the command and the service file. > > # systemctl restart nfs-server > Failed to restart nfs-server.service: Unit

[systemd-devel] Are logs at /run/log/journal automerged?

2022-08-22 Thread Yuri Kanivetsky
Hi, I'm experiencing this on Digital Ocean. The machine id there changes (which I think shouldn't happen) on the first boot (supposedly by cloud-init). In Ubuntu 22.04 droplets, where logs are stored at /var/log/journal, that leads to journalctl outputting no records (because the log for the new m

Re: [systemd-devel] nfs-convert.service

2022-08-22 Thread Steve Dickson
Thanks for the reply! On 8/22/22 4:09 AM, Lennart Poettering wrote: On Fr, 19.08.22 11:21, Steve Dickson (ste...@redhat.com) wrote: Hello, I'm trying to remove nfsconvert from Fedora but I'm getting the following systemd error after I removed the command and the service file. # systemctl r

Re: [systemd-devel] nfs-convert.service

2022-08-22 Thread Steve Dickson
On 8/22/22 9:46 AM, Steve Dickson wrote: Thanks for the reply! On 8/22/22 4:09 AM, Lennart Poettering wrote: On Fr, 19.08.22 11:21, Steve Dickson (ste...@redhat.com) wrote: Hello, I'm trying to remove nfsconvert from Fedora but I'm getting the following systemd error after I removed the

Re: [systemd-devel] nfs-convert.service

2022-08-22 Thread Tomasz Torcz
On Fri, Aug 19, 2022 at 11:21:49AM -0400, Steve Dickson wrote: > Hello, > > I'm trying to remove nfsconvert from Fedora but I'm > getting the following systemd error after I removed > the command and the service file. > > # systemctl restart nfs-server > Failed to restart nfs-server.service: Unit

[systemd-devel] logging for socket-based services

2022-08-22 Thread Allison Sherburne
Hello, I have recently ported a number of xinetd services to systemd socket-based services. The services are working as expected but my logs are now flooded with "systemd: Started ..." messages. Is there any way to tune the logging for these services to filter out these entries?

Re: [systemd-devel] logging for socket-based services

2022-08-22 Thread Mantas Mikulėnas
As far as I know, only "[Service] LogLevelMax=notice" can hide those messages, but it also has the side effect of discarding *all* lower-level log messages generated by the service (even through syslog or journal APIs), so IMO it's kind of a last-resort option. But if your services receive so many