systemd: Yet Another Init Replacement

zodmaner · 2011-05-20 08:54:05

sand_man wrote:

falconindy wrote:
Separate /var is fine. It will never support separate /usr.
Does anyone have /usr on a separate partition? I don't think I ever have.
I do in FreeBSD but that's different.

I used separate /usr on my netbook, which have two SSD with very limited storage space, one 4GB and another 16GB.

hauzer · 2011-05-20 09:29:48

sand_man wrote:

Does anyone have /usr on a separate partition? I don't think I ever have.
I do in FreeBSD but that's different.

I had it untill a day ago for about two months, just for the kicks. But I've merged it with / to try out systemd.

XZS · 2011-05-20 10:13:36

falconindy wrote:

findmnt [...] lsblk [...] (util-linux 2.19) tool for looking at actual block devices.

Now that is a nice tool. And in such a basic package.

falconindy wrote:

Feel free to mangle the package as you see fit.

sed -i '/^\(initscripts\|sysvinit\)$/d' /var/lib/pacman/local/systemd-26-1/desc

Farwell, old sysvinit.

falconindy wrote:

Create a symlink to /dev/null for the mount unit you want obliterated

I tried this at first. Though these units kept listed as failed in systemctl list-units. Seemingly, meanwhile an update fixed that. Now they are gone.

falconindy wrote:

XZS wrote:
/etc/locale.conf: LANG=de_DE.utf8
I'd say you failed to set your locale in /etc/locale.conf. See 'man locale.conf'.

The locale.conf worked fine ever since. As WorMzy pointed out, /etc/profile.d/locale.sh was the culprit.

So everything is fixed now. Thanks for the quick solutions.

reflexing · 2011-05-21 18:38:50

Systemd fails booting with latest kernel26 from testing (maybe it is because of udev or other new packages, dunno).

It brings in emergency shell and freeze if I try to continue.

Here is dmesg:

[   96.473512] systemd[1]: Job dev-mapper-arch\x2dboot.device/start timed out.
[   96.473570] systemd[1]: Job local-fs.target/start failed with result 'dependency'.
[   96.473578] systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
[   96.473787] systemd[1]: Job var-lock.mount/start failed with result 'dependency'.
[   96.473835] systemd[1]: Job dbus.service/start failed with result 'dependency'.
[   96.473866] systemd[1]: Job console-kit-daemon.service/start failed with result 'dependency'.
[   96.473875] systemd[1]: Job dbus.socket/start failed with result 'dependency'.
[   96.473883] systemd[1]: Job var-run.mount/start failed with result 'dependency'.
[   96.473892] systemd[1]: Job var.mount/start failed with result 'dependency'.
[   96.473919] systemd[1]: Job fsck@dev-mapper-arch\x2dvar.service/start failed with result 'dependency'.
[   96.473940] systemd[1]: Job mnt-media.mount/start failed with result 'dependency'.
[   96.473971] systemd[1]: Job fsck@dev-mapper-arch\x2dmedia.service/start failed with result 'dependency'.
[   96.473992] systemd[1]: Job home.mount/start failed with result 'dependency'.
[   96.474023] systemd[1]: Job fsck@dev-mapper-arch\x2dhome.service/start failed with result 'dependency'.
[   96.474303] systemd[1]: Job boot.mount/start failed with result 'dependency'.
[   96.474312] systemd[1]: Job dev-mapper-arch\x2dboot.device/start failed with result 'timeout'.
[   97.096838] systemd[1]: Startup finished in 6s 154ms 716us (kernel) + 1min 30s 942ms 50us (userspace) = 1min 37s 96ms 766us.

Obviously it fails on mounting filesystems. I have my partitions on LVM. I don't know how to get more verbose details...

litemotiv · 2011-05-21 19:50:05

reflexing wrote:

Systemd fails booting with latest kernel26 from testing (maybe it is because of udev or other new packages, dunno).
Obviously it fails on mounting filesystems. I have my partitions on LVM. I don't know how to get more verbose details...

And the normal init works okay?

reflexing · 2011-05-21 20:04:03

litemotiv wrote:

reflexing wrote:
Systemd fails booting with latest kernel26 from testing (maybe it is because of udev or other new packages, dunno).
Obviously it fails on mounting filesystems. I have my partitions on LVM. I don't know how to get more verbose details...
And the normal init works okay?

Yep, normal init boots fine. Forgot to mention that i'm using systemd-git and systemd-arch-units-git form AUR.

falconindy · 2011-05-21 20:48:50

I can reproduce this. it's udev/mkinitcpio related. You'll need to modify the LVM udev rule as mentioned in FS#24272:

https://bugs.archlinux.org/task/24272

Make sure to generate your initramfs after making the change. My non-root LVM volumes work just fine with the modified rule.

reflexing · 2011-05-21 21:08:44

falconindy wrote:

I can reproduce this. it's udev/mkinitcpio related. You'll need to modify the LVM udev rule as mentioned in FS#24272:
https://bugs.archlinux.org/task/24272
Make sure to generate your initramfs after making the change. My non-root LVM volumes work just fine with the modified rule.

Thanks, boots like a charm now.

BasT · 2011-05-23 19:15:28

I just set systemd (27-2 from [community]) up and the one thing that doesn't work is rebooting:

shutdown[23134]: shutting down for system reboot
systemd-initctl[23140]: Received environment initctl request. This is not implemented in systemd.

I found this thread on the [systemd-devel] mailinglist regarding this problem but haven't figured out how to correctly fix it:
http://lists.freedesktop.org/archives/s … 00434.html
(setting an environment variable?)

The other solution I found here (http://lists.freedesktop.org/archives/s … 00072.html) fixes the problem by creating certain symlinks but that would break the use of sysvinit, right? I'd prefer keeping that fallback option for now.

Last edited by BasT (2011-05-23 19:16:36)

falconindy · 2011-05-23 19:23:17

Great, but how did you try to reboot to get that error?

Rebooting here via 'reboot', 'init 6', or 'systemctl reboot' all work just fine.

BasT · 2011-05-23 19:45:14

It happens when I use the Reboot button from the KDE menu.

Rebooting from console seems to work fine.

falconindy · 2011-05-23 20:47:19

So the question then becomes: how are you starting KDE? Are you using KDM? Have you enabled pam_systemd.so in /etc/pam.d/kdm? Do you have a proper consolekit session?

BasT · 2011-05-23 21:12:26

falconindy wrote:

So the question then becomes: how are you starting KDE? Are you using KDM?

Yes.

Have you enabled pam_systemd.so in /etc/pam.d/kdm?

No. Should I? Currently there is no /etc/pam.d/kdm.

Do you have a proper consolekit session?

console-kit-daemon.service is running. I followed the wiki on that issue:

archwiki wrote:

On KDE start an error message will appear saying "console-kit-daemon.unit" could not be found. To solve this problem install systemd-arch-units.

reflexing · 2011-05-24 09:18:06

BasT wrote:

falconindy wrote:
So the question then becomes: how are you starting KDE? Are you using KDM?
Yes.
Have you enabled pam_systemd.so in /etc/pam.d/kdm?
No. Should I? Currently there is no /etc/pam.d/kdm.
Do you have a proper consolekit session?
console-kit-daemon.service is running. I followed the wiki on that issue:
archwiki wrote:
On KDE start an error message will appear saying "console-kit-daemon.unit" could not be found. To solve this problem install systemd-arch-units.

Try this (from Gentoo wiki):

Note: KDM will fail to reboot/halt because /sbin/halt and /sbin/reboot are no longer in the system, so as a workaround you can create a wrapper to the systemd equivalents:
File: /usr/local/sbin/reboot

#!/bin/sh
/bin/systemctl reboot

File: /usr/local/bin/halt

#!/bin/sh
/bin/systemctl halt

Then add/edit this section to the file at /usr/share/config/kdm/kdmrc (or changing it via systemsettings)

File: /usr/share/config/kdm/kdmrc

[Shutdown]
HaltCmd=/usr/local/sbin/halt
RebootCmd=/usr/local/sbin/reboot

I think we should add this to the wiki too, yes, Falconindy?

falconindy · 2011-05-24 10:12:28

No, it shouldn't be added, because the community package requires sysvinit, meaning /sbin/reboot and /sbin/halt still exist.

No. Should I? Currently there is no /etc/pam.d/kdm.

Ah, it's called kde, not kdm. and yes.

Last edited by falconindy (2011-05-24 10:15:29)

Zom · 2011-05-24 10:13:31

reflexing wrote:

Try this (from Gentoo wiki):
Note: KDM will fail to reboot/halt because /sbin/halt and /sbin/reboot are no longer in the system, so as a workaround you can create a wrapper to the systemd equivalents:
File: /usr/local/sbin/reboot
#!/bin/sh
/bin/systemctl reboot
File: /usr/local/bin/halt
#!/bin/sh
/bin/systemctl halt
Then add/edit this section to the file at /usr/share/config/kdm/kdmrc (or changing it via systemsettings)
File: /usr/share/config/kdm/kdmrc
[Shutdown]
HaltCmd=/usr/local/sbin/halt
RebootCmd=/usr/local/sbin/reboot
I think we should add this to the wiki too, yes, Falconindy?

This is only needed if you remove sysvinit, IIRC.

E: That's what I get for not refreshing before posting, I suppose.

Last edited by Zom (2011-05-24 10:15:03)

Zom · 2011-05-24 12:00:24

falconindy wrote:

Have you enabled pam_systemd.so in /etc/pam.d/kdm?

This seems like a good idea to be honest. I had no idea about this.

So, reading man pam_systemd, and as far as I understand it, the example section basically had it nailed down pretty well:

session    required     pam_systemd.so kill-user=1

This will ensure anything started in the kde session is killed when you log out/reboot/halt the computer, right?

I should probably add this to the wiki...

E: Oh. Perhaps I should start reading the wiki a bit more closely then.

Last edited by Zom (2011-05-24 12:35:28)

falconindy · 2011-05-24 12:11:58

The wiki already mentions this. If anything, the wiki should merely refer people to the man page to let them figure out what options make sense for their setup. I personally prefer the default behavior, as the man page also mentions:

Note that setting kill-user=1 or even kill-session=1 will break tools like screen(1)

franz1789 · 2011-05-25 10:57:55

I have a problem with systemd: everytime my system halt "improprerly" (and this happens sometimes, since I am on a notebook) when I boot into archlinux systemd says emergency mode, ask me for ctrl-d or root pass. Well, there's no way to make it boot, if I press ctrl-d it simply repeat those line, if I give my root pass it brings me in a root console, I do a fsck and all is ok. systemctl default just fails, saying that's destructive (or stuff like that).. what to do?

sidneyk · 2011-05-25 15:24:41

franz1789 wrote:

I have a problem with systemd: everytime my system halt "improprerly" (and this happens sometimes, since I am on a notebook) when I boot into archlinux systemd says emergency mode, ask me for ctrl-d or root pass. Well, there's no way to make it boot, if I press ctrl-d it simply repeat those line, if I give my root pass it brings me in a root console, I do a fsck and all is ok. systemctl default just fails, saying that's destructive (or stuff like that).. what to do?

Not trying to come across as unhelpful, but did you follow the wiki on systemd? Are you trying to boot up to a graphical environment, like Gnome or KDE, or such? Did you include the kernel command line option in your grub config.? Someone here can probably get you pointed in the right direction, but we need a little more info.

reflexing · 2011-05-25 15:38:20

franz1789 wrote:

I have a problem with systemd: everytime my system halt "improprerly" (and this happens sometimes, since I am on a notebook) when I boot into archlinux systemd says emergency mode, ask me for ctrl-d or root pass. Well, there's no way to make it boot, if I press ctrl-d it simply repeat those line, if I give my root pass it brings me in a root console, I do a fsck and all is ok. systemctl default just fails, saying that's destructive (or stuff like that).. what to do?

I am also experiencing this bug.

falconindy · 2011-05-25 17:21:27

Sounds like /etc/mtab isn't a symlink to /proc/self/mounts. If that isn't the case, you'll need to post your /etc/fstab.

Last edited by falconindy (2011-05-25 17:21:46)

reflexing · 2011-05-25 20:50:39

falconindy wrote:

Sounds like /etc/mtab isn't a symlink to /proc/self/mounts. If that isn't the case, you'll need to post your /etc/fstab.

Of course it is a symlink. Here is my /etc/fstab:

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0
/dev/mapper/arch-home /home ext4 defaults,user_xattr 0 1
/dev/mapper/arch-media /mnt/media xfs defaults 0 1
/dev/mapper/arch-root / ext4 defaults 0 1
/dev/mapper/arch-swap swap swap defaults 0 0
/dev/mapper/arch-var /var reiserfs defaults 0 1
/dev/mapper/arch-boot /boot ext2 defaults 0 1
none /proc/bus/usb usbfs devgid=108,devmode=664 0 0

falconindy · 2011-05-25 21:03:14

groan. right. you're using LVM.

@franz1789: also on LVM?

This isn't something I've seen myself under these conditions. There's always been accompanying dependencies which failed to start as well. Booting with systemd.log_level=debug will be useful here.

franz1789 · 2011-05-25 22:40:26

since I never followed the lvm archwiki (and since I didn't even know what was it) I think that no, I'm not using it

should I add systemd.log_level=debug to kernel line in grub or which file should I edit otherwise?

Arch Linux

#651 2011-05-20 08:54:05

Re: systemd: Yet Another Init Replacement

#652 2011-05-20 09:29:48

Re: systemd: Yet Another Init Replacement

#653 2011-05-20 10:13:36

Re: systemd: Yet Another Init Replacement

#654 2011-05-21 18:38:50

Re: systemd: Yet Another Init Replacement

#655 2011-05-21 19:50:05

Re: systemd: Yet Another Init Replacement

#656 2011-05-21 20:04:03

Re: systemd: Yet Another Init Replacement

#657 2011-05-21 20:48:50

Re: systemd: Yet Another Init Replacement

#658 2011-05-21 21:08:44

Re: systemd: Yet Another Init Replacement

#659 2011-05-23 19:15:28

Re: systemd: Yet Another Init Replacement

#660 2011-05-23 19:23:17

Re: systemd: Yet Another Init Replacement

#661 2011-05-23 19:45:14

Re: systemd: Yet Another Init Replacement

#662 2011-05-23 20:47:19

Re: systemd: Yet Another Init Replacement

#663 2011-05-23 21:12:26

Re: systemd: Yet Another Init Replacement

#664 2011-05-24 09:18:06

Re: systemd: Yet Another Init Replacement

#665 2011-05-24 10:12:28

Re: systemd: Yet Another Init Replacement

#666 2011-05-24 10:13:31

Re: systemd: Yet Another Init Replacement

#667 2011-05-24 12:00:24

Re: systemd: Yet Another Init Replacement

#668 2011-05-24 12:11:58

Re: systemd: Yet Another Init Replacement

#669 2011-05-25 10:57:55

Re: systemd: Yet Another Init Replacement

#670 2011-05-25 15:24:41

Re: systemd: Yet Another Init Replacement

#671 2011-05-25 15:38:20

Re: systemd: Yet Another Init Replacement

#672 2011-05-25 17:21:27

Re: systemd: Yet Another Init Replacement

#673 2011-05-25 20:50:39

Re: systemd: Yet Another Init Replacement

#674 2011-05-25 21:03:14

Re: systemd: Yet Another Init Replacement

#675 2011-05-25 22:40:26

Re: systemd: Yet Another Init Replacement

Board footer