[Solved] Numlock on boot (with systemd)

I recently upgraded to systemd. Everything is working extremely well. Except that I am given to understand that systemd no doesn't use /etc/inittab, where I had added the command from the wiki that turns on numlock on each of the virtual terminals. Unfortunately the wiki doesn't have any method to do it with systemd, only the /etc/inittab method.
This means that for a brief while, I had to live with the onerous task of hitting numlock manually. It was one of the worst weeks of my life. My index finger is still raw.
I have come up with a somewhat-solution. I just edited /etc/bash.bashrc and added
if [[ $( tty ) == /dev/tty? ]]; then
setleds +num
fi
to it, which works quite well. It turns on num lock once you're logged in as long as you are on a virtual terminal and not on one of the /dev/pts/* ones.
My question is, is there a better place to do this? Maybe some way to get it to turn on before you're even logged in? It doesn't really matter all that much, I'm just trying to make things "correct."
Last edited by scott_fakename (2012-09-06 20:29:46)

DSpider wrote:
https://wiki.archlinux.org/index.php/Ac … _on_Bootup
Set it in Xorg for whatever DE/WM you use and it will be active when you switch to a tty.
Don't forget to mark it as solved.
Yes, I tried that. I use lxdm and xfce, and setting the numlock=1 option in /etc/lxdm/lxdm.conf turns on numlock in xfce and the light in the consoles, but not the actual numlock itself in consoles.
And Kejpi thanks, I was doing that but when I upgraded to systemd it said those would be taken out "at some point" so I was trying to find out if a permanent solution existed yet. Apparently it does not exist yet, which is fine, I was just curious. So I guess I'll stick with the bashrc method for now.
Thanks for the replies.
--Scott

Similar Messages

[SOLVED] Disabling Bluetooth on boot with systemd

I'm having a nasty-won't-go-away problem with the disabling of the bluetooth module in my Thinkpad X200s.
Resorting to the old Arch way of disabling bluetooth on boot, I added this to my rc.local:
/bin/echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
The thing is, this somehow made my boots hit'n'miss: kernel panics every two boots. As soon as I commented that line from my rc.local... no more kernel panics at boot.
I was still using an rc.conf just with daemons, and in troubleshooting the kernel panics got rid of it and used the systemd way of enabling/disabling services. My problem here is that the bluetooth service seems to be impossible to disable.
I first tried the good ol'
systemctl disable bluetooth.service
Which supposedly disabled bluetooth... but didn't. Even
systemctl stop bluetooth.service
Does not work.
Digging around the interwebs, I found that there are "stronger" ways to disable services with systemd, meaning "masking" services - basically links them to /dev/null
So, I tried masking the bugger...
systemctl mask bluetooth.service
Reboot and... the damn bluetooth is still enabled. Only way that works is to echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable... but I can't do it at boot with rc.local, otherwise I'll get the kernel panics again.
Any ideas?
Last edited by Onyros (2012-08-15 13:10:35)

Onyros wrote:
I'm having a nasty-won't-go-away problem with the disabling of the bluetooth module in my Thinkpad X200s.
Resorting to the old Arch way of disabling bluetooth on boot, I added this to my rc.local:
/bin/echo 0 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable
The thing is, this somehow made my boots hit'n'miss: kernel panics every two boots. As soon as I commented that line from my rc.local... no more kernel panics at boot.
I was still using an rc.conf just with daemons, and in troubleshooting the kernel panics got rid of it and used the systemd way of enabling/disabling services. My problem here is that the bluetooth service seems to be impossible to disable.
I first tried the good ol'
systemctl disable bluetooth.service
Which supposedly disabled bluetooth... but didn't.
It disables the bluetooth service which is very different from what your write to sysfs accomplishes. Don't you really just want to blacklist the bluetooth module? Your post is a bit hard to follow...

[Solved] Automating btrfs scrub with systemd

I have a single disk laptop (no RAID) and would like to have btrfs scrub run automatically on some interval and to be automatically emailed if any errors are found. (My data is backed up online and I can attempt a manual fix.) I'm trying to set this up with systemd and the btrfs tools. Here's what I figure I need:
A systemd service to run btrfs scrub on my entire filesystem.
A systemd timer to schedule this job weekly.
systemd services to pause and resume a running btrfs scrub when the machine suspends and wakes up.
A script to run btrfs status when the previous service has finished, parse the output for the number of errors, and email me if the number is greater than 0.
A systemd service to run that script when the scrub service has completed.
What I have so far is below. I'm sure there are problems with it all, and I'm especially uncertain about #5, since I don't know if the After attribute of one service waits until another has completed or just started. If anyone could take a look and give me some pointers I'd appreciate it very much. (The python script is a hack but I'm more concerned with the systemd at the moment, unless you see obvious problems or improvements you'd like to suggest.)
Attempt at 1 and 2:
/etc/systemd/system/btrfs_scrub.service
[Unit]
Description=Run btrfs scrub on filesystem
[Service]
Type=forking
ExecStart=btrfs scrub start /home
/etc/systemd/system/btrfs_scrub.timer
[Unit]
Description=Weekly btrfs scrub
[Timer]
OnCalendar=weekly
Persistent=true
[Install]
WantedBy=timers.target
Attempt at 3:
/etc/systemd/system/btrfs_cancel.service
[Unit]
Description=Pause a running btrfs scrub on suspend
Before=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub cancel /home
[Install]
WantedBy=suspend.target
/etc/systemd/system/btrfs_resume.service
[Unit]
Description=Resume a paused btrfs scrub after suspend
After=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub resume /home
[Install]
WantedBy=suspend.target
Attempt at 4:
/home/username/Code/Scripts/btrfs_results.py
#Runs btrfs scrub and looks for an indication of errors found, upon
#which an email is sent.
import subprocess
import smtplib
from email.mime.text import MIMEText
def email_alert():
text = "btrfs scrub found errors"
addr = 'myemail@address'
username = 'myusername'
password = 'mypassword'
msg = MIMEText(text)
msg['Subject'] = 'btrfs errors'
msg['From'] = addr
msg['To'] = addr
server = smtplib.SMTP('smtp.gmail.com', '587')
server.starttls()
server.login(username,password)
server.sendmail(addr, addr, msg.as_string())
server.quit()
print('email sent')
def main():
cmd = ['btrfs', 'scrub', 'status', '/home']
output = subprocess.check_output(cmd)
output_str = output.decode("utf-8")
output_words = output_str.split(' ')
for w in range(0, len(output_words)):
if output_words[w].find('error') > -1:
if int(output_words[w - 1]) > 0:
email_alert()
main()
Attempt at 5:
/etc/systemd/system/btrfs_results.service
[Unit]
Description=Parse output from btrfs scrub
Requires=btrfs_scrub.service
After=btrfs_scrub.service
[Service]
Type=oneshot
ExecStart=/usr/bin/python /home/username/Code/Scripts/btrfs_results.py
[Install]
WantedBy=multi-user.target
Last edited by 0112358 (2014-09-16 01:26:21)

0112358 wrote:I have a single disk laptop (no RAID) and would like to have btrfs scrub run automatically on some interval and to be automatically emailed if any errors are found. (My data is backed up online and I can attempt a manual fix.) I'm trying to set this up with systemd and the btrfs tools. Here's what I figure I need:
0112358 wrote:
A systemd service to run btrfs scrub on my entire filesystem.
A systemd timer to schedule this job weekly.
Should not be hard.
0112358 wrote:systemd services to pause and resume a running btrfs scrub when the machine suspends and wakes up.
This happens automatically with s2disk. Am I missing something?
0112358 wrote:A script to run btrfs status when the previous service has finished, parse the output for the number of errors, and email me if the number is greater than 0.
You might want to integrate that in the main btrfs scrub script, just after scrub is completed you will run this. Right?
0112358 wrote:A systemd service to run that script when the scrub service has completed.
0112358 wrote: What I have so far is below. I'm sure there are problems with it all, and I'm especially uncertain about #5, since I don't know if the After attribute of one service waits until another has completed or just started. If anyone could take a look and give me some pointers I'd appreciate it very much. (The python script is a hack but I'm more concerned with the systemd at the moment, unless you see obvious problems or improvements you'd like to suggest.)
0112358 wrote:
Attempt at 1 and 2:
/etc/systemd/system/btrfs_scrub.service
[Unit]
Description=Run btrfs scrub on filesystem
[Service]
Type=forking
ExecStart=btrfs scrub start /home
/etc/systemd/system/btrfs_scrub.timer
[Unit]
Description=Weekly btrfs scrub
[Timer]
OnCalendar=weekly
Persistent=true
[Install]
WantedBy=timers.target
Yes, why not wrap this in some sort of main bash (or python) script.
0112358 wrote:
Attempt at 3:
/etc/systemd/system/btrfs_cancel.service
[Unit]
Description=Pause a running btrfs scrub on suspend
Before=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub cancel /home
[Install]
WantedBy=suspend.target
/etc/systemd/system/btrfs_resume.service
[Unit]
Description=Resume a paused btrfs scrub after suspend
After=suspend.target
[Service]
Type=oneshot
ExecStart=btrfs scrub resume /home
[Install]
WantedBy=suspend.target
Why not do nothing at all? Just let the fs continue after resume. Or is s2disk cancelling this process?
0112358 wrote:
Attempt at 4:
/home/username/Code/Scripts/btrfs_results.py
#Runs btrfs scrub and looks for an indication of errors found, upon
#which an email is sent.
import subprocess
import smtplib
from email.mime.text import MIMEText
def email_alert():
text = "btrfs scrub found errors"
addr = 'myemail@address'
username = 'myusername'
password = 'mypassword'
msg = MIMEText(text)
msg['Subject'] = 'btrfs errors'
msg['From'] = addr
msg['To'] = addr
server = smtplib.SMTP('smtp.gmail.com', '587')
server.starttls()
server.login(username,password)
server.sendmail(addr, addr, msg.as_string())
server.quit()
print('email sent')
def main():
cmd = ['btrfs', 'scrub', 'status', '/home']
output = subprocess.check_output(cmd)
output_str = output.decode("utf-8")
output_words = output_str.split(' ')
for w in range(0, len(output_words)):
if output_words[w].find('error') > -1:
if int(output_words[w - 1]) > 0:
email_alert()
main()
Ok
0112358 wrote:
Attempt at 5:
/etc/systemd/system/btrfs_results.service
[Unit]
Description=Parse output from btrfs scrub
Requires=btrfs_scrub.service
After=btrfs_scrub.service
[Service]
Type=oneshot
ExecStart=/usr/bin/python /home/username/Code/Scripts/btrfs_results.py
[Install]
WantedBy=multi-user.target
Yeah, why not wrap 1,2,4 and 5 into one script/service. Why the fine granularity?

[SOLVED] system not booting with LVM root and systemd

hi everyone ,
I've update my arch installation and performed the upgrade to systemd , and after that the system is not booting , it brings me to a recovery shell .
the root FS is on LVM , and everything under /dev/mapper is missing .
journalctl -xb -p err show me this error :
-- Logs begin at Tue 2013-05-28 21:14:18 CEST, end at Tue 2013-07-23 19:29:38 CEST. --
Jul 23 19:29:35 elminster systemd[1]: Timed out waiting for device dev-mapper-VolGroup00\x2dhome.device.
-- Subject: Unit dev-mapper-VolGroup00\x2dhome.device has failed
-- Defined-By: systemd
-- Unit dev-mapper-VolGroup00\x2dhome.device has failed.
-- The result is timeout.
Jul 23 19:29:35 elminster systemd[1]: Dependency failed for /home.
-- Subject: Unit home.mount has failed
-- Defined-By: systemd
-- Unit home.mount has failed.
-- The result is dependency.
Jul 23 19:29:35 elminster systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Unit local-fs.target has failed.
-- The result is dependency.
Jul 23 19:29:35 elminster systemd[1]: Dependency failed for /home/andrea/DropBox.
-- Subject: Unit home-andrea-DropBox.mount has failed
-- Defined-By: systemd
-- Unit home-andrea-DropBox.mount has failed.
-- The result is dependency.
Jul 23 19:29:35 elminster systemd[1]: Dependency failed for File System Check on /dev/mapper/VolGroup00-home.
-- Subject: Unit systemd-fsck@dev-mapper-VolGroup00\x2dhome.service has failed
-- Defined-By: systemd
-- Unit systemd-fsck@dev-mapper-VolGroup00\x2dhome.service has failed.
-- The result is dependency.
Jul 23 19:29:35 elminster systemd[298]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
-- Subject: Process /bin/plymouth could not be executed
-- Defined-By: systemd
-- The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
here the relevant section of the /etc/fstab
/dev/mapper/VolGroup00-arch_i686_root / ext4 defaults,noatime,nodiratime 0 1
/dev/mapper/VolGroup00-home /home ext4 defaults,noatime,nodiratime 0 2
/dev/sda1 /boot ext4 defaults 0 1
/dev/mapper/VolGroup00-Store /media/store ext4 defaults,noatime,nodiratime 0 2
/dev/mapper/VolGroup00-migration /media/migration ext4 defaults,noatime,nodiratime,noauto 0 2
/dev/mapper/VolGroup00-DropBox /home/andrea/DropBox ext4 rw,noatime,nodiratime 0 0
/dev/mapper/VolGroup00-virtualbox--machines /media/store/virtualbox ext3 rw 0 0
/dev/mapper/VolGroup00-backup /media/backup ext3 rw,relatime,data=ordered 0 0
lvm services are enabled on systemd , but under /dev/mapper i find only /dev/mapper/control , all the other files are missing (list from another install)
ls -l /dev/mapper/*
crw------- 1 root root 10, 236 Jul 23 20:19 /dev/mapper/control
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-arch_i686_root -> ../dm-3
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-debian_root -> ../dm-6
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-DropBox -> ../dm-2
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-home -> ../dm-0
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-Store -> ../dm-1
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-ubuntu1204 -> ../dm-5
lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-virtualbox--machines -> ../dm-4
tried also vgchange -ay from recover shell but still no luck
any clue ?
Last edited by andreagrax (2013-07-26 19:46:12)

andreagrax wrote:lvm services are enabled on systemd
Which?
tried also vgchange -ay from recover shell but still no luck
Did you do vgscan first? What error did you get or did the command just return empty?
Is the lvm2 hook in mkinitcpio.conf? Have you tried regenerating your initramfs?

[solved] Can't boot with LVM and usb external disk

I successfully installed Archlinux on my first computer, using LVM on two internal Hard Drives.
I'm trying to do exactly the same on my second computer, but I got a problem: the LVM volume is not found at boot, so that the root partition can't be mounted and the boot fails.
The only difference is that, on my second computer, the second hard drive is connected through USB.
Some hints: my second computer boots perfectly with LVM and Ubuntu. Archlinux needs to be configured adequately.
I tried to add rootdelay=30 in menu.lst, but it changes nothing. Of course, in /etc/rc.conf I have USELVM="yes" and in /etc/mkinitcpio.conf I have HOOKS="base udev autodetect pata scsi sata keymap lvm2 filesystems"
Thank you for helping me to keep Archlinux on my second computer!
Last edited by Achille (2008-06-29 21:59:09)

I finally solved my problem!
In the file /etc/mkinitcpio.conf, I modified the MODULES loaded:
MODULES="pata_acpi ata_generic ata_piix usbcore usb_storage uhci_hcd ehci_hcd sg scsi_mod sd_mod dm_mod"
I also add in the file /lib/initcpio/hooks/lvm2 the line /bin/sleep 10
/bin/sleep 10
msg "Scanning logical volumes..."
And finally, I ran the command:
mkinitcpio -p kernel26

[SOLVED] Can only boot with error in fstab

Hey there!
During boot I noticed a message, that /dev/sda4 (my /home-partition) gets passed a wrong option.
BUT when the system finished booting, everything works very well!
checking my fstab got me
/dev/sda4 /home ext4 default,noatime 0 2
which I corrected (adding the "s").
my new fstab:
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults,noatime 0 1
/dev/sda4 /home ext4 defaults,noatime 0 2
resulting in the problem, that "/home" isn't accessible and "/" is mounted as new home... (and login with slim doesn't work at all)
any ideas?
thanks for your answers!
Last edited by Slizzered (2010-04-15 05:51:45)

Man, my fstab seems to be really crappy I think now..
(gonna change the order immediately )
more information:
when I log in with tty1 as normal user, it says
No directory, logging in with HOME=/
"mount /home"
gives me:
mount: according to mtab, /dev/sda4 is already mounted on /home
mount failed
however, "ls /home"
gives me just the folder "lost & found" instead of my user-folder

[Solved]No active session with systemd-logind

I've read all the posts on the forum about sytemd and active sessions but I can't seem to get it working.
I'm on a up to date Arch, complete systemd. I'm using GDM as DM and latest version of Gnome.
Output of loginctl show-session $XDG_SESSION_ID
1 Id=2
2 Timestamp=Sun 2013-02-03 21:53:16 CET
3 TimestampMonotonic=14881075
4 DefaultControlGroup=name=systemd:/user/peter/2
5 VTNr=0
6 Display=:0
7 Remote=no
8 Service=gdm-password
9 Leader=2712
10 Audit=2
11 Type=x11
12 Class=user
13 Active=no
14 State=online
15 KillProcesses=no
16 IdleHint=no
17 IdleSinceHint=0
18 IdleSinceHintMonotonic=0
19 Name=peter
Output of systemctl list-unit-files |grep enabled
cups.path enabled
acpid.service enabled
chrony.service enabled
cronie.service enabled
cups.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
display-manager.service enabled
dkms.service enabled
gdm.service enabled
[email protected] enabled
httpd.service enabled
lm_sensors.service enabled
mysqld.service enabled
NetworkManager.service enabled
postfix.service enabled
preload.service enabled
rsyslog.service enabled
syslog.service enabled
systemd-readahead-collect.service enabled
systemd-readahead-drop.service enabled
systemd-readahead-replay.service enabled
thinkfan.service enabled
tlp-init.service enabled
tomcat6.service enabled
[email protected] enabled
unload.service enabled
upower.service enabled
acpid.socket enabled
cups.socket enabled
remote-fs.target enabled
Output of ls -lR /etc/systemd/system
/etc/systemd/system:
total 52K
drwxr-xr-x 2 root root 4.0K Nov 1 22:52 cryptsetup.target.wants/
lrwxrwxrwx 1 root root 46 Sep 24 22:02 dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 default.target.wants/
lrwxrwxrwx 1 root root 35 Jan 28 23:33 display-manager.service -> /usr/lib/systemd/system/gdm.service
drwxr-xr-x 2 root root 4.0K Nov 8 09:10 getty.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:36 graphical.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 local-fs.target.wants/
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 multi-user.target.wants/
drwxr-xr-x 2 root root 4.0K Oct 9 09:49 printer.target.wants/
-rw-r--r-- 1 root root 216 Feb 3 21:09 rc-local.service
drwxr-xr-x 2 root root 4.0K Nov 7 23:28 shutdown.target.wants/
drwxr-xr-x 2 root root 4.0K Nov 3 20:43 sockets.target.wants/
drwxr-xr-x 2 root root 4.0K Jan 13 16:58 sysinit.target.wants/
lrwxrwxrwx 1 root root 39 Nov 3 20:39 syslog.service -> /usr/lib/systemd/system/rsyslog.service
drwxr-xr-x 2 root root 4.0K Feb 3 21:42 system-update.target.wants/
-rw-r--r-- 1 root root 166 Nov 7 23:28 unload.service
/etc/systemd/system/cryptsetup.target.wants:
total 0
lrwxrwxrwx 1 root root 42 Nov 1 22:52 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/default.target.wants:
total 0
lrwxrwxrwx 1 root root 57 Feb 3 21:42 systemd-readahead-collect.service -> /usr/lib/systemd/system/systemd-readahead-collect.service
lrwxrwxrwx 1 root root 56 Feb 3 21:42 systemd-readahead-replay.service -> /usr/lib/systemd/system/systemd-readahead-replay.service
/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Nov 8 09:10 [email protected] -> /usr/lib/systemd/system/[email protected]
/etc/systemd/system/graphical.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Sep 26 22:31 tlp-init.service -> /usr/lib/systemd/system/tlp-init.service
lrwxrwxrwx 1 root root 38 Nov 3 20:36 upower.service -> /usr/lib/systemd/system/upower.service
/etc/systemd/system/local-fs.target.wants:
total 0
/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 37 Nov 3 20:43 acpid.service -> /usr/lib/systemd/system/acpid.service
lrwxrwxrwx 1 root root 38 Nov 7 23:10 chrony.service -> /usr/lib/systemd/system/chrony.service
lrwxrwxrwx 1 root root 38 Sep 24 22:04 cronie.service -> /usr/lib/systemd/system/cronie.service
lrwxrwxrwx 1 root root 33 Oct 9 09:49 cups.path -> /usr/lib/systemd/system/cups.path
lrwxrwxrwx 1 root root 36 Oct 11 18:03 dkms.service -> /usr/lib/systemd/system/dkms.service
lrwxrwxrwx 1 root root 37 Sep 26 18:54 httpd.service -> /usr/lib/systemd/system/httpd.service
lrwxrwxrwx 1 root root 42 Jan 14 22:47 lm_sensors.service -> /usr/lib/systemd/system/lm_sensors.service
lrwxrwxrwx 1 root root 38 Nov 8 10:53 mysqld.service -> /usr/lib/systemd/system/mysqld.service
lrwxrwxrwx 1 root root 46 Sep 24 22:02 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 39 Oct 3 12:00 postfix.service -> /usr/lib/systemd/system/postfix.service
lrwxrwxrwx 1 root root 39 Oct 1 23:21 preload.service -> /usr/lib/systemd/system/preload.service
lrwxrwxrwx 1 root root 40 Jan 13 16:58 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 39 Nov 3 20:39 rsyslog.service -> /usr/lib/systemd/system/rsyslog.service
lrwxrwxrwx 1 root root 40 Sep 24 22:21 thinkfan.service -> /usr/lib/systemd/system/thinkfan.service
lrwxrwxrwx 1 root root 39 Oct 5 16:27 tomcat6.service -> /usr/lib/systemd/system/tomcat6.service
/etc/systemd/system/printer.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Oct 9 09:49 cups.service -> /usr/lib/systemd/system/cups.service
/etc/systemd/system/shutdown.target.wants:
total 0
lrwxrwxrwx 1 root root 34 Nov 7 23:28 unload.service -> /etc/systemd/system/unload.service
/etc/systemd/system/sockets.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Nov 3 20:43 acpid.socket -> /usr/lib/systemd/system/acpid.socket
lrwxrwxrwx 1 root root 35 Oct 9 09:49 cups.socket -> /usr/lib/systemd/system/cups.socket
/etc/systemd/system/sysinit.target.wants:
total 0
/etc/systemd/system/system-update.target.wants:
total 0
lrwxrwxrwx 1 root root 54 Feb 3 21:42 systemd-readahead-drop.service -> /usr/lib/systemd/system/systemd-readahead-drop.service
The solution posted here https://bbs.archlinux.org/viewtopic.php … 0#p1186900 with the rc.local compatubility service does work in a way. I created an empty rc.local file and made it executable. Now GDM is not starting until I hit CTRL-C, and after that my session is active!
I use the latest version of Polkit and initscripts is not installed.
Any tip is welcome!
Last edited by pgrond (2013-02-24 17:55:31)

I've read that post but I can't get it fixed. I don't need any rc-local compatibility. I'm on a complete systemd system, so I don't get why I would need this.
If I create a dummy rc-local service GDM won't start. But after a CTRL-C it will start and the session is active. Can it be some sort of race condition?
Or can it be a problem that my home partition is encrypted and mounted on login?

Slow boot with systemd due to NetworkManager and laptop-mode-tools

ernestas ~ $ systemd-analyze blame
25787ms NetworkManager.service
3440ms laptop-mode-tools.service
1792ms systemd-logind.service
1573ms systemd-modules-load.service
1519ms home.mount
1305ms polkit.service
977ms systemd-udevd.service
903ms systemd-sysctl.servic
What could be the underlying problem? How do I solve it?

Okay. I no longer use laptop-mode-tools, but NetworkManager still seems to be slow:
ernestas ~ $ systemd-analyze blame
3592ms NetworkManager.service
3013ms systemd-logind.service
869ms dev-sda7.swap
762ms home.mount
666ms systemd-modules-load.service
546ms systemd-udev-trigger.service
523ms systemd-udevd.service
500ms dev-hugepages.mount
479ms sys-kernel-debug.mount
Last edited by ernetas (2012-11-03 16:01:44)

MOVED: How to disable numlock on boot with X79A-GD45?

This topic has been moved to MSI Intel boards.
https://forum-en.msi.com/index.php?topic=253397.0

And the reason of duplicating your thread is?

Help with systemd problems/reply to closed thread

@Everyone; as the previopus topic was closed, I am opening a new one here, partly to reply to some things that was said to me in the previous thread/topic (and I do not like to leave people hanging), but mainly to try and get some help with my systemd config (that I was not able to find help with in the wiki or manpages).
@czubek; eww, that sounds rather similiar to some other operating systems I've heard of (not just, but obviously including, windows)... For me, subjectively, that is not very attractive, as being able to have a single application do a single thing, and then mixing and matching as I personally see fit is a great thing.
@tomegun: I can indeed see your point, but if I made direct quotes on all the things I reply too, my posts would reach biblical proportions.
Mmm-hmm, I do indeed know of "the Arch Way"; however, the system that you expose can be of varying complexity as well, and I found that the system that was presented to me by way of Sysvinit/initscripts was a way simpler system than that presented to me by systemd.
Indeed, and I do like that; I enjoy knowing how my system works and learning more about it; however, the truth is that reading manpages and the wiki isn't always enough. And I use the numbers instead of letters in certain places as a jest, please, do not get offended by that; if you have to, get offended by my opinions.
Ah, I have now scanned the wiki, the manpages, and have already faced problems. While part of me is saddened by this fact (as I was hoping for a smooth transition to systemd), part of me is glad that I can at least prove that everything isn't quite as simple as some people would make it out to be. More on this later in this post, as I do need help with the problems I have faced.
And I wouldn't say that the new and old way are equally trivial, as I immediatley faced problems with "the new way". More on this later.
Ok, I find that if the debate is polarized, then there is nothing wrong with describing it as such. I spell what I see.
Oh my... Ignored as a matter of principle? I would say that that is an excellent way to stagnate; by that logic, moviemakers, gamemakers etcetera should ignore any and all criticism they recieve, as the critics are not contributing.... Wouldn't that lead to a complete halt in development? Isn't criticism (so long as it is constructive, obviously) a key component of (media/software) evolution?
Ah, I see, then I misunderstood the current state of the install media
"Some adjustements"... Well, I guess we'll have to see how that goes, then. Hopefully it'll be smooth.
@Everyone; Awebb possesses stunning accuracy as far as his observations go.
@zb3; My point exactly.
@tomegun; I believe you to be wrong; complaining (but not whining) is the first step towards improvement, as I think that I and zb3 has shown.
Further, your last point (where you talk about "deep understanding of Y" and whatnot) is basically saying that only devs and programmers can contribute, so zb3's observation would be correct.
Also, making suggestions is part of constructive criticism; you can do that even if you can't code, e.g. by saying "X works badly because it makes Y crash; couldn't we replace X with something akin to Z?". This is a valid point even if you have no intricate understanding of X, Y or Z, and if it is impossible to replace X for one reason or the other, it's not hard to reply with "Replacing X is impossible because of reason Q", and then see if someone can solve reason Q etcetera.
zb3's example is obviously helping; for one, it would allow people to know taht they can't boot with systemd in certain cases, or that installing/runing systemd can break their system. I would consider that rather important information.
@Everyone; Now then, to see if I can (or rather, if I can get help to) shed some light on some problems I've been having.
My transition to systemd went pretty smooth (besides the fact that I couldn't use 'systemctl' to set anything, and neither duckduckgo nor any posts in the forums could help me (the error I continously got was "Failed to issue method call: Launch helper exited with unknown return code 1") and that there are no manpages/tips on how to configure the files for "localtime" and "adjtime", which would've been good considering some syntax have changed) to about halfway through, to the point where I was supposed to start using systemd for my daemons.
Now then, to the main problem; first, I tried running
"systemctl enable syslog-ng.service"
and got the following message;
"ln -s '/usr/lib/systemd/system/syslog-ng.service' '/etc/systemd/system/syslog.service'
ln -s '/usr/lib/systemd/system/syslog-ng.service' '/etc/systemd/system/multi-user.target.wants/syslog-ng.service'"
Since it doesn't exclusively say that something went wrong (at least as far as I can understand), I pondered the message a bit, but moved on to try and start dbus by issuing
"systemctl enable dbus.service",
to which I got the reply
"The unit files have no [Install] section. They are not meant to be enabled using systemctl."
This I can only assume is an error message of some sort, especially seeing as it says "not meant to be enabled using systemctl", but the wiki rather explicitly states that that is what I am supposed to do.
I dare not move on (or attempt to start other daemons) without further advice, as I fear I might break my system. Any ideas as to how to solve this would be greatly appreciated.

tcmdvm wrote:
The message;
"ln -s '/usr/lib/systemd/system/syslog-ng.service' '/etc/systemd/system/syslog.service'
ln -s '/usr/lib/systemd/system/syslog-ng.service' '/etc/systemd/system/multi-user.target.wants/syslog-ng.service'"
indicates that running "systemctl enable syslog.service" is now enabled.
If you try running sytemtctl enable <whatever>.service and get
"The unit files have no [Install] section. They are not meant to be enabled using systemctl." means there is no <whatever>.service file available to enable.
The dbus.service as far as I know is already enabled when installing systemd and doesn't require any action.
Ah, right, systemd is chatty (I'm of the old skool; if nothing is/goes wrong, a program should keep quiet).
Oh ok, then I should dare more on.
ZekeSulastin wrote:To be a bit more precise, it means the service is there but it's only used as a dependency for something else; the [Install] section of the file is what tells systemctl where to link it and such. Also, where exactly in the wiki were you told explicitly to 'systemctl enable dbus.service'? I can easily point you to the sections in both installation guides that tell you how to set things like /etc/localtime et. al (also `man 7 archlinux`), but not the one that said to manually enable dbus.
Ah, I see; and well, I was told right here, going from the top, to "Enable Daemons formerly listed in rc.conf [...] For a translation of the daemons from /etc/rc.conf to systemd services, see: List of Daemons and Services.", and, using the list, dbus is mentioned there, as you can see. Since I started from the top, I did not know that you didn't need to enable that service. Perhaps it could be added to the descriptions of the relevant services in the Wiki which ones are autostarted?
ZekeSulastin wrote:Lastly, I don't think trying to continue conversations from a closed thread is a very good idea, let alone doing it in a giant undivided wall of text that makes it quite difficult to pick out much any single topic.
Meh, I directly refer to the relevant people, they can easily see their own old posts in the previous thread, etcetera... I think te ones who have something to say will be able to find my replies to their previous statements (or so I hope). For now, as everyone can see, I quote stuff (but man might I make some huge posts if I ever post again in the future, if I quote what I reply to).
fsckd wrote:This is not really a technical support subforum. Moving from Arch Discussion to Newbie Corner.
Ah ok, thanks (or perhaps a cautious thanks? Moving it to "newbie corner" might, after all, be a subtle insult...).
tomegun wrote:It is not really possible to follow your message as you don't quote what you are replying to. Moreover, as the thread was closed I think that means we should stop the discussion ;-)
Hmm, I think it means cop-out for lack or proper arguments/responses... But ok, I'll let it slide, for now (mainly as I can't do much else).
tomegun wrote:You are not meant to enable dbus.service as it is enabled unconditionally. To check the enabled/disabled state of your services try "systemctl list-unit-files". "static" means that you are not supposed to enabled/disable it.
Ah ok, thank you. Now, having abandoned all hope, I'll start configuring again and see how it goes... May the void protect me. If I die, grieve not for me, but remember me in the fight against hard-to-configure applications.
(edit/addon)
Actually, what am I supposed to do with "hwclock"? the List of Daemons only says that I shouldn't run that in tandem with ntpd, but I'm not running ntpd, so... How do I get hwclock with systemd?
Edited for additional question.
Last edited by incassum (2012-11-07 08:44:42)

[SOLVED] RTC and dual booting with Windows 8/8.1

I am planning ahead of installing Arch on a windows 8.1 laptop, and need to understand whether or not the known Windows registry hack to get windows to use UTC for the RTC is still valid for Windows 8/8.1? I have been searching via google and the usual sources of information, but it is not clear to me if there are problems doing this, specifically if arch is dual booted with Windows 8/8.1 rather than older versions of the MS OS. Certainly I have used the technique without any problem in the past when dual booting Windows XP with Arch on several different machines.
Does anyone have personal experience with doing this on a Windows 8 or 8.1 machine and can report here on whether it works successfully or not?
Thanks for any advice.
Last edited by mcloaked (2014-02-11 21:16:21)

Since there were no replies at this point I thought I would just go ahead and implement the registry hack on the Windows 8.1 O/S in the laptop and see if Windows behaves. It appears to be OK, with the displayed time being correct after reboot, and time synchronisation remaining fine with no problems seen in the displayed time, although I won't be able to read the RTC directly until I have completed the Arch install in the coming week or two. I now don't foresee any issues with the time synchronisation between booting Arch and Windows 8.1 so I will mark this as solved.
Since the RTC is now in UTC then normal clock config in Arch using chrony should perform normally once the install is done and the new system set up.
Last edited by mcloaked (2014-02-11 21:17:11)

[Solved] Running mpd as user mpd with systemd without using mpd.conf

Maybe this is tivial, but I searched about an hour without any results. I want to run mpd as user mpd. I cant use the mpd config file since mpd set the UID and GID explicitely resulting in mpd not having the necessary supplementary groups to access the locally shared music on my pc. Well I tried to run mpd with systemd by
# systemctl start mpd
and the systemd contains the user mpd
$ cat /etc/systemd/system/default.target.wants/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
User=mpd
ExecStart=/usr/bin/mpd --no-daemon
# allow MPD to use real-time priority 50
LimitRTPRIO=50
LimitRTTIME=-1
# move MPD to a top-level cgroup, as real-time budget assignment fails
# in cgroup /system/mpd.service, because /system has a zero real-time
# budget; see
# http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/
ControlGroup=cpu:/mpd
# assign a real-time budget
ControlGroupAttribute=cpu.rt_runtime_us 500000
[Install]
WantedBy=default.target
but it did not run as mpd.
Well how can I run mpd as mpd? Is there a way to do it like with dropbox: dropbox@<user>.service
Last edited by manuelschneid3r (2015-03-25 12:52:52)

Glad you solved it. Was just typing a response and I'll still add two remarks:
The ps|grep output showed that you run grep as root, not mpd itself (which won't have a space in the command -- the second time it only worked because the mpd group is preceded by a space).
It sounds like it took you a while to find the drop-in configuration snippet in the mpd.service.d directory. These drop-in are shown in `systemctl status`, which is something you'd normally check in situations like these, and that might help to discover them more quickly.
Last edited by Raynman (2015-03-25 12:58:36)

[Solved] postgresql with systemd

Hello Guys,
I'm having problems starting the postgres with systemd.
Following errors:
Running systemctl start postgresql
k@archK ~ % sudo systemctl start postgresql
Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
1 k@archK ~ %
Running systemctl status postgresql.service got the message below:
k@archK ~ % systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled)
Active: failed (Result: exit-code) since Sáb, 2012-12-29 19:09:19 BRT; 1min 19s ago
Process: 1746 ExecStart=/usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120 (code=exited, status=1/FAILURE)
Process: 1741 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/postgresql.service
3 k@archK ~ %
and journalctl -xn this:
k@archK ~ % sudo journalctl -xn
[sudo] password for k:
-- Logs begin at Sáb, 2012-12-29 03:47:42 BRT, end at Sáb, 2012-12-29 19:11:49 BRT. --
Dez 29 19:09:19 archK systemd[1]: postgresql.service: control process exited, code=exited status=1
Dez 29 19:09:19 archK systemd[1]: Failed to start PostgreSQL database server.
-- Subject: Unit postgresql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit postgresql.service has failed.
-- The result is failed.
Dez 29 19:09:19 archK systemd[1]: Unit postgresql.service entered failed state
Dez 29 19:09:19 archK sudo[1738]: pam_unix(sudo:session): session closed for user root
Dez 29 19:11:27 archK udisks-daemon[430]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Dez 29 19:11:27 archK udisks-daemon[430]: helper(pid 1781): launched job udisks-helper-ata-smart-collect on /dev/sda
Dez 29 19:11:28 archK udisks-daemon[430]: helper(pid 1781): completed with exit code 0
Dez 29 19:11:28 archK udisks-daemon[430]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Dez 29 19:11:49 archK sudo[1786]: k : TTY=pts/0 ; PWD=/home/k ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Dez 29 19:11:49 archK sudo[1786]: pam_unix(sudo:session): session opened for user root by k(uid=0)
Here is the postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
and /etc/conf.d/postgresql
## Parameters to be passed to postgresql
## Default data directory location
PGROOT="/var/lib/postgres"
## Passed to initdb if necessary
INITOPTS="--locale en_US.UTF-8"
## Default log file location
#PGLOG="/var/log/postgresql.log"
## Additional options to pass via pg_ctl's '-o' option
#PGOPTS=""
Does anyone have any idea how to fix this?
Thanks.
Last edited by kleitonkk (2013-01-03 23:51:41)

Sorry for the delay, was traveling and just returned yesterday.
lothar_m was followed as described in the post, since removed the packages twice and did the install again but the same error.
[root@archK conf.d]# systemctl start postgresql
Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
[root@archK conf.d]#
systemctl status postgresql.service
➜ ~ systemctl status postgresql.service
postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; disabled)
Active: failed (Result: exit-code) since Thu, 2013-01-03 18:14:43 BRT; 9min ago
Process: 10897 ExecStart=/usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120 (code=exited, status=1/FAILURE)
Process: 10892 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/postgresql.service
➜ ~
[root@archK conf.d]# journalctl -xn
-- Logs begin at Wed, 2013-01-02 16:50:57 BRT, end at Thu, 2013-01-03 18:34:41 BRT. --
Jan 03 18:25:28 archK su[11082]: pam_unix(su:session): session opened for user root by k(uid=1000)
Jan 03 18:34:36 archK systemd[1]: Starting PostgreSQL database server...
-- Subject: Unit postgresql.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- Unit postgresql.service has begun starting up.
Jan 03 18:34:36 archK postgres[11127]: LOG: could not translate host name "localhost", service "5432" to address: Name or service not known
Jan 03 18:34:36 archK postgres[11127]: WARNING: could not create listen socket for "localhost"
Jan 03 18:34:36 archK postgres[11127]: FATAL: could not create any TCP/IP sockets
Jan 03 18:34:41 archK postgres[11127]: pg_ctl: could not start server
Jan 03 18:34:41 archK postgres[11127]: Examine the log output.
Jan 03 18:34:41 archK systemd[1]: postgresql.service: control process exited, code=exited status=1
Jan 03 18:34:41 archK systemd[1]: Failed to start PostgreSQL database server.
-- Subject: Unit postgresql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit postgresql.service has failed.
-- The result is failed.
Jan 03 18:34:41 archK systemd[1]: Unit postgresql.service entered failed state
/usr/lib/systemd/system/postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
➜ ~ pacman -Q |grep postgres
postgresql 9.2.2-2
postgresql-libs 9.2.2-2
➜ ~
/etc/conf.d
## Parameters to be passed to postgresql
## Default data directory location
PGROOT="/var/lib/postgres"
## Passed to initdb if necessary
INITOPTS="--locale en_US.UTF-8"
## Default log file location
#PGLOG="/var/log/postgresql.log"
## Additional options to pass via pg_ctl's '-o' option
#PGOPTS=""
/usr/lib/systemd/system/postgresql.service
[Unit]
Description=PostgreSQL database server
After=network.target
[Service]
Type=forking
TimeoutSec=120
User=postgres
Group=postgres
Environment=PGROOT=/var/lib/postgres
SyslogIdentifier=postgres
PIDFile=/var/lib/postgres/data/postmaster.pid
ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGROOT}/data
ExecStart= /usr/bin/pg_ctl -s -D ${PGROOT}/data start -w -t 120
ExecReload=/usr/bin/pg_ctl -s -D ${PGROOT}/data reload
ExecStop= /usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m fast
# Due to PostgreSQL's use of shared memory, OOM killer is often overzealous in
# killing Postgres, so adjust it downward
OOMScoreAdjust=-200
[Install]
WantedBy=multi-user.target
I'm still looking for how to solve.
Thank you.

[SOLVED] samba does not start properly again -this time with systemd

Definitely no luck with this one...
So, today I've switched to a pure systemd init system, and noticed that I have this old issue again.
(Link to my old thread: https://bbs.archlinux.org/viewtopic.php?id=142704)
Samba doesn't start properly again, more precisely smbd is launched but not nmbd, so samba is not working as it should (for example smbtreee lists nothing).
Last time I've solved it by putting samba long before networkmanager in the daemons array, but with systemd I'm a bit confused...
Anyone has this issue?
Last edited by scar (2012-11-03 07:05:42)

I think that nmbd isn't waiting for networkmanager to start on my system, because I'm getting journal entries like
Oct 31 00:47:21 spacebar winbindd[431]: [2012/10/31 00:47:21.556005, 0] param/loadparm.c:7969(lp_do_parameter)
Oct 31 00:47:21 spacebar systemd[1]: nmbd.service: main process exited, code=exited, status=1
Oct 31 00:47:21 spacebar systemd[1]: Unit nmbd.service entered failed state.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): carrier now ON (device state 20)
Oct 31 00:47:22 spacebar kernel: r8169 0000:03:00.0: eth0: link up
Oct 31 00:47:22 spacebar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Auto-activating connection 'Static'.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) starting connection 'Static'
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Oct 31 00:47:22 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Oct 31 00:47:22 spacebar rpc.mountd[462]: Version 1.2.6 starting
Oct 31 00:47:22 spacebar systemd[1]: Startup finished in 3s 850ms 155us (kernel) + 21s 279ms 972us (userspace) = 25s 130ms 127us.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Oct 31 00:47:23 spacebar ntpd_intres[441]: DNS 0.au.pool.ntp.org -> 116.66.160.39
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Policy set 'Static' (eth0) as default for IPv4 routing and DNS.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Activation (eth0) successful, device activated.
Oct 31 00:47:23 spacebar NetworkManager[391]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Oct 31 00:47:23 spacebar dbus[401]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.771872, 0] param/loadparm.c:7969(lp_do_parameter)
Oct 31 00:47:20 spacebar smbd[428]: Ignoring unknown parameter "user client driver"
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.794252, 0] lib/interface.c:543(load_interfaces)
Oct 31 00:47:20 spacebar smbd[428]: WARNING: no network interfaces found
Oct 31 00:47:20 spacebar smbd[428]: [2012/10/31 00:47:20.805126, 0] smbd/server.c:1109(main)
Oct 31 00:47:20 spacebar smbd[428]: standard input is not a socket, assuming -D option
Oh, this started happening after putting a MUCH faster cpu and motherboard in the system, so maybe there's a race-condition there?
Last edited by MisterAnderson (2012-10-30 04:59:46)

[SOLVED] filesystem 2014.07-1 + systemd 215: cannot boot

Hi!
With latest systemd + filesystem, i was no more able to boot.
Systemd fails to start initrd-switch-root.service; downgrading (lib)systemd(-sysvcompat) only is not enough, I had to downgrade filesystem too, to be able to boot.
There is probably a problem with the /etc/os-release move (i guess). I tried symlinking /usr/lib/os-release to /etc-osrelease (*after i downgraded to systemd 214*, so i had only filesystem 2014.07) and it failed anyway.
And obviously emergency shell did not show up (don't ask me the reason why...) even if OnFailure says it calls emergency.target...
Last edited by nierro (2014-07-06 07:43:36)

Hi!
This seems not be fixed for any non default kernel! At least a one successful boot with the default kernel (of Archlinux) is required or maybe the mentioned recreation of the mkinitcpip with a custom-kernel also fixes this. So in other words:
Everyone who doesn't use the Archlinux-Kernel needs to be instructed to rebuild the mkinitcpio for the custom kernel or a reboot with the kernel supplied by Archlinux.
// update
Probably this fix for systemd 215-2 trigger the creation "to late" i.e. not during the upgrade itself?
[2014-07-20 18:12] [PACMAN] upgraded systemd (214-2 -> 215-4) # the upgrade through pacman
lrwxrwxrwx 1 root root 21 Jul 20 18:36 /etc/os-release -> ../usr/lib/os-release # time of my first successfull reboot
Last edited by hoschi (2014-07-20 17:24:43)

[Solved] Numlock on boot (with systemd)

Similar Messages

Maybe you are looking for