Just upgraded for Fedora 32, still running NUS/ypserv, now getting
very slow logins and systemd-logind is not starting. I enabled debug
logs and am seeing the below logs. I don't think
https://github.com/systemd/systemd/issues/7074 is back with the
nss-nis bug but I made sure that IPAddress= is set
Hi Lennart,
On Tue, May 19, 2020 at 11:26 PM Lennart Poettering
wrote:
> So, yes, "systemd-makefs" was how I intended this originally to be
> done. However, I think that's not going to suffice in the long run,
> and instead systemd-repart will soon be able to format file systems
> natively by inv
On Di, 19.05.20 23:05, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> to partition the new drive. That works nicely. Now how do I format
> those partitions? Systemd-mkfs springs to mind -- so I will need to
> identify those partitions in /etc/fstab. My system is immutable, so I
> have to create
Hello!
I am experimenting with automatically partitioning, formatting and
creating files on a new drive based on configuration. Systemd comes
with all the building blocks nowadays to do this, but I am still
struggling a bit.
I have created some partition definitions and ran systemd-repart to
part
Thanks Lennart for replying.
If I get you correctly we can hit this issue for both of the below cases
1. Reloading unit file via daemon-reload while the services are executing and
2. Services are active and we try to disable or mask a service without
stopping it?
I apologize if I sound too repeti
On Di, 19.05.20 20:47, Debraj Manna (subharaj.ma...@gmail.com) wrote:
> Thanks Michael for replying and giving me the issue details.
>
> I am trying to understand in what scenarios we may hit this issue. I
> checked the issue. It states that "This can happen when the
> configuration is changed and
Thanks Michael for replying and giving me the issue details.
I am trying to understand in what scenarios we may hit this issue. I
checked the issue. It states that "This can happen when the
configuration is changed and reloaded while we are executing a
service.". Can you also please explain what d
Hey list,
systemd-timesyncd has an Alias=dbus-org.freedesktop.timesync1.service and
an accompanying dbus service file too.
It is started in early boot; `Before=sysinit.target` so why would making
it dubs-activatible ever make sense? It is always started way before
dbus.service itself is started
On Mon, 18 May 2020, Debraj Manna wrote:
> Around the same time I am seeing the below error in syslog
>
> May 18 08:49:24 platform3 systemd[1]: Removed slice User Slice of support.
> May 18 08:49:27 platform3 systemd[1]: Assertion 's->type ==
> SERVICE_ONESHOT' failed at ../src/core/service.c:1792
