[systemd-devel] troubleshooting different behaviour of systemd between f16 and f18

Lennart Poettering lennart at poettering.net
Tue Feb 12 18:26:10 PST 2013

On Mon, 11.02.13 13:37, Thierry Parmentelat (thierry.parmentelat at inria.fr) wrote:

> Hi
> Feel free to redirect me to some other place if needed :)
> So, we have a BootCD that is intended for remotely managed machines
> In a nutshell, we need to redefine the whole init sequence, and what we had on f12 and f14 boxes was essentially a set of 2 init scripts, one for rough system initialization (pl_sysinit), and one for downloading a stage2 python script (pl_boot), in this order of course
> ----
> I'd done the job of adapting to systemd for f16 at the time; my approach had been as simple as it gets (for legacy reasons we're going to have the 2 scripts around anyway, so optimizing all that in a systemd-specific way is not yet in order unfortunately)
> So in the boot image I had only
> * created(replaced?) a symlink 
> # ls -l /etc/systemd/system/default.target
> lrwxrwxrwx 1 root root 34 Feb 11 08:12 /etc/systemd/system/default.target -> /etc/systemd/system/pl_boot.target
> * and added 2 files
> ==> /etc/systemd/system/pl_boot.service <==
> [Unit]
> Description=pl_boot service
> [Service]
> ExecStart=/etc/init.d/pl_boot
> ExecStartPre=/etc/init.d/pl_sysinit
> Type=oneshot

Is pl_sysinit supposed to leave processes around? This is not allowed anymore.


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list