Hi,
I'm not sure if I'm writing to the right mailing list, please
redirect me if I'm wrong.
I'm trying to make some custom initramfs image with systemd and I
encounter very strange behaviour. Namely, when I boot into it with
"root=/dev/hda" kernel command line option the boot process stops right
On 09/14/2016 01:31 AM, Michal Koutny wrote:
> Currently one PID can belong up to two services
> (manager->watch_pids{1,2}). If more than one why just two? And when can
> such a situation happen?
I've found origin of this change in [1]. Still, I wonder why it is
"interesting to map a PID to two
Hello Anton,
Anton Gerasimov [2016-09-19 18:08 +0200]:
> I'm trying to make some custom initramfs image with systemd and I
> encounter very strange behaviour. Namely, when I boot into it with
> "root=/dev/hda" kernel command line option the boot process stops right
> after "Reached target Basic
19.09.2016 20:24, Martin Pitt пишет:
>
> Does your problem happen at every boot, or only sometimes? In the
> former case it might actually not be a race condition but a more
> systematic error, such as missing some udev rules, or not
> re-triggering all udev devices during boot, etc.
>
I also found that when i start
docker run --rm -it --security-opt=seccomp:unconfined --cap-add
SYS_ADMIN --cap-add MKNOD -v /sys/fs/cgroup:/sys/fs/cgroup:ro
fedora-25-image bash
and then run the systemd (so that it is not pid 1)
/lib/systemd/systemd --system --show-status=true
