On Sun, 12.09.10 23:44, Piavlo (pia...@cs.bgu.ac.il) wrote: > > Hi Jens, > > Thanks for you reply > > > If I may guess. Stuff started with @ are not "real" services. Those you > > have to delete manually in the wants directory, i.e > > /etc/systemd/system/getty.target.wants. > > > I think it's the right way but the wrong place. "ln -s > > /lib/systemd/system/serial-ge...@.service > > /etc/systemd/system/getty.target.wants/serial-ge...@ttys0.service" > > That should start the getty at boot. > > What I did instead is created > /lib/systemd/system/serial-getty.target > similar to /lib/systemd/system/getty.target
Thou shalt not fiddle with /lib/systemd/system. /lib/systemd/system is private property of the packaging system, i.e. rpm. If you want to make changes, do so in /etc/systemd/system, which is the first place systemd looks for everything. Only when that dir is empty we fall back to /lib/systemd/system. Note that there is really no need for a serial-getty.target. Also, recent systemd versions (>= 9) will spawn a getty on the configured kernel console anyway. > Another strange problem I have is that "network.service" is not started > upon boot automatically. There's a bug in rhbz open about this: https://bugzilla.redhat.com/show_bug.cgi?id=630225 Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
