[Solved] systemd and fstab with /var bind

I'm having some troubles migrating to systemd. I have the following in my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid,size=8G 0 0
UUID=2bedbb1a-015f-4c46-ab48-f3ffc55b154b /boot ext2 defaults 0 1
#UUID=2c5f02a3-c8a1-45ed-92f4-dc09e56c09d7 /var ext4 discard,noatime 0 1
UUID=2c5f02a3-c8a1-45ed-92f4-dc09e56c09d7 /mnt/mythtv ext4 discard,noatime 0 1
UUID=910898cb-2d67-4689-ba51-358d94b2531d swap swap defaults 0 0
UUID=cac6ccea-456a-4c09-a1db-57cec02b238d / ext4 discard,noatime 0 1
/dev/mapper/VolGroupArray-lvmedia /mnt/media ext4 auto 0 0
mnt/media/var /var bind defaults,bind 0 0
(/dev/sda is an ssd disk so I decided to move /var to my software raid and lvm disks)
However this doesn't seem to work anymore with systemd as it doesn't get mounted automatically anymore. I've setup a debug console, there I can mount it by simply typing mount /var and then I can manually start the services that failed.
didn't actually solve the bind stuff, but decided to make a new partition on the lvm disk and mount /var there.
Last edited by blahbla77 (2012-11-18 13:58:13)

Are you really missing a leading / from the last line?

Similar Messages

[SOLVED]systemd and make a camera visible GUI-wise in your filemanager

After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
fine.But when connecting the camera again it is not visible graphically.
The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
In the wiki again, this time about digital cameras
Permission issues
Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
$ ck-list-sessions | grep TRUE
active = TRUE
is-local = TRUE
ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
Should not be necessary when it has worked before systemd and earlier experiences
But what is this about "Permission issues"? Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
[leif@krasaki ~]$ ck-list-sessions | grep TRUE
is-local = TRUE
active = TRUE
is-local = TRUE
[leif@krasaki ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:12:56.499847Z'
login-session-id = '1'
idle-since-hint = '2012-10-24T07:13:26.994037Z'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:13:02.361157Z'
login-session-id = '1'
[leif@krasaki ~]$
As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
From the wiki:
In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
[leif@krasaki ~]$ loginctl
SESSION UID USER SEAT
1 1000 leif seat0
1 sessions listed.
[leif@krasaki ~]$ loginctl show-session 1
Id=1
Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
TimestampMonotonic=20040019
DefaultControlGroup=name=systemd:/user/leif/1
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=315
Audit=1
Type=tty
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=yes
IdleSinceHint=1351069009642296
IdleSinceHintMonotonic=6664433
Name=leif
[leif@krasaki ~]$
Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
Thanks for reading...

Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

[solved] systemd and tftpd

[edited for additional question clarity]
[edited again showing result of running in.tftpd manually]
I have a recently installed systemd based machine with 2 NICs. One faces the LAN and runs dhcpcd, the other faces a local isolated subnet and runs dhcpd and tftpd.
Everything was working until an update early this week (including the new 3.6.9 kernel) caused the eth0 and eth1 to swap places.
I tried a udev rule to assign the eth0 and eth1, but it didn't seem to work.
Subsequently, I just renemaed the eth0 and eth1 in the dhcpd.service file and the /etc/conf.d/network file referenced by the network.service file.
Now dhcpd4 seems to be working, but tftpd is continuing to fail to start with the error:
Dec 12 09:36:57 beezey in.tftpd[1386]: cannot bind to local IPv4 socket: Address already in use
Dec 12 09:36:57 beezey systemd[1]: tftpd.service: main process exited, code=exited, status=71/n/a
Dec 12 09:36:57 beezey systemd[1]: Unit tftpd.service entered failed state
The tftpd.service file:
[root@beezey johnea]# cat /etc/systemd/system/tftpd.service
[Unit]
Description=hpa's original TFTP daemon
[Service]
ExecStart=/usr/sbin/in.tftpd -l -4 -s /srv/tftp/
StandardInput=socket
StandardOutput=inherit
StandardError=journal
[Install]
WantedBy=multi-user.target
I've used the network.service file indicated here:
https://wiki.archlinux.org/index.php/Co … IP_address
Including this file to configure the static eth0:
[root@beezey johnea]# cat /etc/conf.d/network
interface=eth0
address=10.20.30.1
netmask=24
broadcast=10.20.30.255
And started and stopped tftpd.socket prior to .service as instructed here:
https://wiki.archlinux.org/index.php/Tf … er#Systemd
Netstat show the IPv6 port 69 for tftpd, but there is no port 69 listening on IPv4:
[root@beezey johnea]# netstat --udp --tcp -l -n
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6012 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6013 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:6010 :::* LISTEN
tcp6 0 0 ::1:6011 :::* LISTEN
tcp6 0 0 ::1:6012 :::* LISTEN
tcp6 0 0 ::1:6013 :::* LISTEN
udp 0 0 0.0.0.0:58493 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 10.20.30.1:123 0.0.0.0:*
udp 0 0 192.168.13.73:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp6 0 0 :::32138 :::*
udp6 0 0 :::69 :::*
udp6 0 0 fe80::21b:21ff:fe6b:123 :::*
udp6 0 0 fe80::1a03:73ff:fe3:123 :::*
udp6 0 0 ::1:123 :::*
udp6 0 0 :::123 :::*
I'm able to start in.tftpd manually via:
[root@beezey johnea]# in.tftpd -l -s /srv/tftp/
After this command line netstat shows the active socket 69 on IPv4 and IPv6:
[root@beezey johnea]# netstat --udp -l -n
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 0.0.0.0:44194 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 0.0.0.0:69 0.0.0.0:*
udp 0 0 192.168.13.73:123 0.0.0.0:*
udp 0 0 10.20.30.1:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp6 0 0 :::41398 :::*
udp6 0 0 :::69 :::*
udp6 0 0 fe80::21b:21ff:fe6b:123 :::*
udp6 0 0 fe80::1a03:73ff:fe3:123 :::*
udp6 0 0 ::1:123 :::*
udp6 0 0 :::123 :::*
I'm unclear on:
1) why tftpd thinks IPv4 0.0.0.0:69 is already in use
2) how to best configure persistent interface names under sytemd and udev
Any guidance is greatly appreciated...
johnea
Last edited by android (2012-12-14 00:20:19)

OK, I have it working. There were several things wrong:
1) The modified tftpd.service file was incorrect. The introduction of the '-l' flag, to run tftpd as a standalone service, not inetd driven, was preventing the socket based unit from working. The tftpd.service file below is working correctly with the stock tftpd.socket file provided with the tftp-hpa package. This file has modifications to make tftpd run only on the statically configured interface.
[Unit]
Description=hpa's original TFTP daemon on subnet interface sub0
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/in.tftpd -a 10.20.30.1 -s /srv/tftp/
StandardInput=socket
StandardOutput=inherit
StandardError=journal
[Install]
WantedBy=multi-user.target
The "Requires=network.target" and "After=network.target" were necessary additions for restricting tftpd to one interface by it's IP address.
The "-a 10.20.30.1" argument specifies the interface to monitor.
2) The /etc/conf.d/network file had typos.
The statically configured interface uses the network.service file specified here:
https://wiki.archlinux.org/index.php/Tf … er#Systemd
However my /etc/conf.d/network file somehow managed to pick up spaces at the beginning of the lines after the first line. This prevented the network.service file from extracting the parameters.
I additionally modified the network.service file by commenting out the wpa_supplicant line, and the "ip route add" line, because this is a wired interface and it is a local subnet with no outbound gateway.
The netstat output was misleading me. Since the tftpd unit is socket driven, it does not show up as a listening socket on port 69 (this also kept it out of ps listings). I believe systemd had started tftpd.socket and was monitoring UDP port 69. This is why I was experiencing the "Address already in use" error on the tftpd.service file that specified the '-l' option.
The persistent interface names where established via a Udev rule, as specified here:
https://wiki.archlinux.org/index.php/Ud … ork_device
This led to custom interface names, which required the /etc/conf.d/network file, and other network config files be updated.
These steps led to a working tftpd service on one statically configured interface only.
The only remaining systemd issue to be resolved on this host is to restrict the dhcpcd client to the other interface only, but that's another post.
johnea

[SOLVED] Systemd and tmpfiles? Conflicting /tmp?

I've got this error in journal;
systemd-tmpfile[247]: Two or more conflicting lines for /tmp configured, ignoring.
This is from a leftover from arch initscripts, /usr/lib/tmpfiles.d/arch.conf shich is doubled by systemd's, /usr/lib/tmpfiles.d/x11.conf (almost).
arch.conf;
D /tmp 1777 root root 10d
d /run/daemons 0755 root root -
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
F /run/utmp 0664 root utmp -
r /tmp/.X[0-9]-lock
r /etc/nologin
r /etc/shutdownpid
r /forcefsck
r /fastboot
x11.conf;
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Make sure these are created by default so that nobody else can
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
# Unlink the X11 lock files
r /tmp/.X[0-9]*-lock
Can I delete the arch one - where is it started from at boot? I'm running only systemd and got rid of all arch units. Or can I merge them? I really can't tell which tmpfiles are needed.
Last edited by swanson (2012-05-31 19:11:46)

Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

[solved]systemd and console font

Hi guys. I've just switched my laptop over to systemd and so far I'm finding it great! I am, however, having a slight issue with getting it to set a console font, err, properly.
KEYMAP=uk
FONT=Lat2-Terminus16
Before switching to systemd, this worked fine. However now when I boot up, the font is set early (I have the hook in mkinitcpio.conf) but once I get to the login screen, the screen flickers and I end up back on the default font. I've tried this with several of the available fonts and it happens with all of them. I don't have it set anywhere else, so I'm not sure why the font is being reset. Has anyone else come across this issue yet?
Cheers.
Last edited by JHeaton (2012-08-25 20:20:34)

bohoomil wrote:Did you really rebuild the initramfs? Once it becomes a part of your boot image, it shouldn't be reset (which happens when the video driver like nouveau gets loaded: if this is the case, add your video driver to the MODULES array in /etc/mkinitcpio,conf and rebuild the image again). I have been doing the very same thing every time I prepare a new setup and it always works as expected.
Yes, I did rebuild it. I didn't have the video driver in MODULES though; adding it has now solved the issue. Don't know why I hadn't added i915 to that array though.
Thanks very much for your help.

[SOLVED] Systemd has problems with ntfs-3g

Hi!
I created a custom daemon.
It's very simple.
[Unit]
Description=Mounting partitions if Im at home
[Service]
Type=simple
ExecStart=/home/skitter/homemount.sh
[Install]
WantedBy=multi-user.target
And the content of a script:
#!/bin/bash
device0="/dev/disk/by-uuid/e2b0e86b-d377-4699-9407-48d56eb439d0"
if [ -b "$device0" ]
then
mount UUID=01CECC33AEE58980 /mnt/WINDOWS
mount UUID=ff2d44b5-bdd0-4524-89bf-6ac3bc005887 /mnt/Other
mount UUID=599D77CD384A8B00 /mnt/Files
fi
Unfortunately for some reason the ntfs partitions are being automatically unmounted.
The ext4 partition is not causing any problems.
$sudo systemctl status homemount
homemount.service - Mounting disk if Im at home
Loaded: loaded (/usr/lib/systemd/system/homemount.service; enabled)
Active: inactive (dead) since Sun 2013-10-27 21:56:23 CET; 1s ago
Process: 3202 ExecStart=/home/skitter/homemount.sh (code=exited, status=0/SUCCESS)
Main PID: 3202 (code=exited, status=0/SUCCESS)
Oct 27 21:56:22 archer ntfs-3g[3206]: Mounted /dev/sdb1 (Read-Write, label "", NTFS 3.1)
Oct 27 21:56:22 archer ntfs-3g[3206]: Cmdline options: rw
Oct 27 21:56:22 archer ntfs-3g[3206]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
Oct 27 21:56:22 archer ntfs-3g[3206]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3213]: Version 2013.1.13 external FUSE 29
Oct 27 21:56:23 archer ntfs-3g[3213]: Mounted /dev/sda1 (Read-Write, label "Files", NTFS 3.1)
Oct 27 21:56:23 archer ntfs-3g[3213]: Cmdline options: rw
Oct 27 21:56:23 archer ntfs-3g[3213]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096
Oct 27 21:56:23 archer ntfs-3g[3213]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3206]: Unmounting /dev/sdb1 ()
Last edited by Skitter (2013-10-27 21:43:32)

I think this is because the mount command exits, so the daemon is then considered dead (or completed). But I am not entirely sure about this.
A better solution would be to simply make an entry in your fstab with the noauto,x-systemd.automount,nofail options. This would essentially achieve what you are after I think. You could also make actualy systemd.mount and systemd.automount units as well, though these would automagically be generated by an entry in your fstab.
If you are unsure of what exactly to put in native systemd units, you can always see what systemd does in /run/systemd/generators. In fact, if you put a fstab entry for this ntfs-3g mount, let it generate (ie reboot, or run the generator) then check out that directory, you can simply pull those units out of there, give them an [Install] section, and enable them.

[SOLVED] systemd switch, problems with slim/bootup

My system will boot, giving me "OK" for everything it's doing. Then my system gives me a tty login prompt, but continues booting:
gestalt login: [ OK ] Starting Wicd.
[ OK ] Reached target multi-user.
[ OK ] Reached target graphical interface.
So if i just hit enter, it gives me another login prompt, then I can login, but X/fluxbox isn't started or anything.
My ~/.xinitrc:
exec startfluxbox
xset +fp /usr/share/fonts/local
xset fp rehash
systemctl list-units --type=target
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target masked active active graphical.target
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded active active Syslog
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
14 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Graphical target isn't masked, like I thought it would be after reading this
systemctl status slim.service gives me:
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Mon, 2012-11-26
Process: 305 ExecStart=urs/bin/slim -nodaemon(code=exited, status =1/FAILURE)
CGroup: name=systemd:/system/slim.service
systemd-analyze blame gives (just going to ignore the times)
wicd.service
systemd-vconsole-setup.service
systemd-binfmt.service
systemd-logind.service
systemd-modules-load.service
dev-hugepages.mount
systemd-udev-trigger.service
dev-mqueue.mount
systemd-udevd.service
proc-sys-fs-binfmt_service.mount
console-kit-daemon.service
polkit.service
systemd-tmpfiles-setup.service
home.mount
systemd-sysctl.service
tmp.mount
systemd-user-sesssions.service
systemd-remount-fs.service
slim isn't even on this list.
systemctl --failed
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
slim.service loaded failed failed SLiM Simple Login Manager
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Hopefully this isn't too much information (or completely irrelevant) for what might be a far simpler problem, but I'm just not sure what's going on. It might be worth noting that I only bothered to start switching to systemd today when I had to reboot and slim wouldn't start/get me into my WM(!) This is interesting to me, since I read (somewhere) that as of slim's last version, it would only work with systemd and not consolekit... but when I try:
pacman -Qi slim
It tells me that the last time I last updated/installed slim was November 5 of this year. Any ideas?
EDIT:
Latest nVidia drivers weren't working with my 7xxx integrated GPU. Downgrade to 304xx drivers or use nouveau.
Last edited by brokengestalt (2012-11-28 17:41:50)

I tried starting X manually (typing in "startx" at the prompt, and I get the following errors:
modprobe: ERROR: could not insert 'nvidia': No such device
Fatal server error:
no screens found
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
It looks like I'm just having problems with my video card, but I have the proprietary nVidia drivers installed and X installed. The systemd wiki page mentions no changes that I would need to make to my xorg or nvidia configuration...

[SOLVED] systemd and ntpd.service

I've just converted to pure systemd according to the wiki. Everything went remarkably well, with just a little blemish. While I'm not notified of any error at startup, when I check systemctl I find that ntpd.service's LOAD/ACTIVE/SUB is loaded/failed/failed.
systemctl status ntpd.service gives me this:
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
Active: failed (Result: exit-code) since Thu, 18 Oct 2012 04:16:56 +0200; 6s ago
Process: 1397 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
Main PID: 1398 (code=exited, status=255)
CGroup: name=systemd:/system/ntpd.service
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
and journalctl pretty much more of the same:
Oct 18 04:16:56 mike ntpd[1397]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 18 04:16:56 mike ntpd[1398]: proto: precision = 0.106 usec
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike sudo[1394]: pam_unix(sudo:session): session closed for user root
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
Oct 18 04:16:56 mike systemd[1]: ntpd.service: main process exited, code=exited, status=255
Oct 18 04:16:56 mike systemd[1]: Unit ntpd.service entered failed state.
Trying to use it manually (eg. ntpd -qg) works, so I'm not sure what's wrong with it exactly. Where else should I look?
Last edited by Mr_Mario (2012-12-06 11:29:57)

slickvguy wrote:I've just started converting to systemd and ran into the same issue. I believe the problem is that you are missing the ntp group from your group file. If you updated your system and merely renamed your group.pacnew to group, it no longer contains the ntp group that was previously added. I just added the ntp group again ( ntp:x:87: ), and ntp started properly and the status is correct. Hope this helps.
That was it. Thank you!

[SOLVED] systemd and pm-utils quirks (gma500_gfx)

Hi,
I have a netbook with the infamous poulsbo/gma500 chipset. To suspend it on the console (I am not yet at X ;-) ) I need to add the --quirk-vbemode-restore option to pm-suspend as described in the wiki [1]. How can I get the same effect when migrating to systemd (and therefore switching to systemctl and dropping pm-utils)?
Thanks
[1] https://wiki.archlinux.org/index.php/Poulsbo
Last edited by olaf.the.lost.viking (2012-08-22 23:13:22)

The code is in /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler and /usr/lib/pm-utils/sleep.d/99video. The substantial part is
# save/restore the vbe mode
vbe_savemode() { vbe vbemode get |savestate vbemode; }
vbe_restoremode()
# this is a little mode complicated to handle special-casing mode 3.
local vbemode=$(restorestate vbemode)
if [ "$vbemode" = "3" ]; then
vbe vgamode set $vbemode
else
vbe vbemode set $vbemode
fi
Note that vbe function only forwards its arguments to vbetool. You could place something like this into /usr/lib/systemd/system-sleep/99video
#!/bin/sh
TMPFILE=/tmp/gma500-state
vbe_savemode() {
vbetool vbemode get > $TMPFILE
vbe_restoremode() {
# this is a little mode complicated to handle special-casing mode 3.
local vbemode=$(cat $TMPFILE)
if [ "$vbemode" = "3" ]; then
vbetool vgamode set $vbemode
else
vbetool vbemode set $vbemode
fi
if [[ $1 == "pre" ]]; then
vbe_savemode
elif [[ $1 == "post" ]]; then
[ -O /tmp/gma500-state ] && vbe_restoremode
fi

Systemd and fstab[solved easily]

hey guys,
another computer, another question about the switch to systemd.
My computer won't boot if there is anything in fstab besides / .
anything else in there (mostly removable stuff by uuid), and boot hangs. I'm once again missing something obvious, I'm sure.
As far as I can tell everything else is error-free and working fine.
any ideas? thanks!
Last edited by scrawler (2012-10-29 02:11:23)

WorMzy wrote:Posting your fstab might help..
+1
Solved or not, providing more info will very likely help others finding this thread via a search. Please post your before and after /etc/fstab to the thread when you get a chance.
Last edited by graysky (2012-10-29 14:06:01)

[SOLVED] systemd and rc-local.service

So, today i decided to try a pure systemd system by migrating my old installation.
The first problem i faced comes from rc-local.service.
I followed this:
https://wiki.archlinux.org/index.php/Sy … s#rc.local
and created an identical rc-local.service:
/etc/systemd/system/rc-local.service
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=oneshot
ExecStart=/etc/rc.local
TimeoutSec=0
StandardInput=tty
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
...made it executable and enabled the service via
systemctl enable rc-local.service
The problem comes when i issue:
systemctl --system daemon-reload
systemctl start rc-local.service
Here the prompt hangs forever.
..so i reeboted and automagically "Something" of my rc.local has been executed.
What has been left out was a subscript launched in background from my rc.local.
While in the past my working rc.local executed a script:
checkmounts.sh & #<-this loops forever
...and in ps -ef|grep checkmounts i got it listed, now with systemd i haven't it anymore.
...note that to debug issues i echoed several "marks" into a text file, and i'm sure that
rc.local has been executed till the end and systemctl status reports no errors at all.
So the question are:
1) why can't i start rc-local from terminal via sysctl and it works (sort of) if i reboot?
2) why a script executed from rc.local in background doesn't work?
Last edited by kokoko3k (2012-08-27 15:43:35)

I already tried that with the same results.
Now i found that removing StandardInput=tty works and solved both of the issues (at least issuing manual startups).
So this:
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=oneshot # is forking instead of oneshot needed here?
ExecStart=/etc/rc.local
TimeoutSec=0
#StandardInput=tty
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Works really well for me, exactly like in the past.
Plus, i can see all running child processess via systemctl status rc-local.service
If someone thinks this is wrong for seome reason i'll NOT update the wiki page.
--EDIT
Works well after a reboot too, and changing Type= to fork make just fork, parallelizing the boot (kdm+kde for me)
Last edited by kokoko3k (2012-09-13 13:43:38)

[SOLVED] Systemd and Sshfs Automount

Hi,
I'm trying to set up automount on an sshfs drive. From other posts I already concluded this line for my /etc/fstab:
[email protected]:/users/schnitzl /home/ben/data/mnt/uni/ fuse.sshfs noauto,x-systemd.automount,users,idmap=user,IdentityFile=/home/ben/.ssh/id_rsa,allow_other,reconnect 0 0
But yet it does not work. Whilst logging into the remote Host from command line is no problem:
ssh [email protected],
automounting fails:
-- cd uni/
bash: cd: uni/: No such device.
journalctl -b | grep uni tells me:
Nov 15 16:31:31 mario systemd[1]: Mounting /home/ben/data/mnt/uni...
Nov 15 16:31:31 mario systemd[1]: Mounted /home/ben/data/mnt/uni.
Nov 15 16:31:31 mario systemd[1]: home-ben-data-mnt-uni.mount mount process exited, code=exited status=1
Nov 15 16:31:31 mario systemd[1]: Unit home-ben-data-mnt-uni.mount entered failed state.
Any Ideas?
Benjamin
Edit: Which services do I have to restart, in order to let systemd reload the /etc/fstab configuartion?
Last edited by Lord Bo (2012-11-15 17:06:55)

Thank you very much! That was the right option! I already had it there, but as it did not work yet, I altered the line and forgot to add this option... . However: one last thing: Which services do I have to restart, after having altered /etc/fstab in order to take changes into effect? It is a bit annoying always having to restart the whole system.
Edit:
teekay wrote:EDIT: sorry, I oversaw the noauto. So you want on-demand, right? https://bbs.archlinux.org/viewtopic.php?id=146674
Well it is now mounted on demand (as soon, as I try to access the directory).
And the link you provided: I already found that during my researches, but the crucial point was, as you mentioned, the missing _netdev option. However: Thanks again .
Last edited by Lord Bo (2012-11-15 16:54:52)

[SOLVED] systemd and ConsoleKit - I'm a little confused

I'm using SLIM and Openbox and am in the process of converting to systemd.
I've added the needed configuration files for systemd.
I can boot using the wiki instructions here https://wiki.archlinux.org/index.php/Sy … stallation
I've added SLIM as a service using https://wiki.archlinux.org/index.php/Sy … er_systemd
My question is: Do I still need ConsoleKit? So far this seems to be working for me but I'm not sure if I need to add ConsoleKit somehow.
BTW: I start Openbox with the usual
exec ck-launch-session openbox-session
when using initscripts.
Last edited by bergersau (2012-10-11 05:31:52)

Thanks WonderWoofy, I just double checked my ~/.xinitrc and found I had commented out ck-launch-session when I installed SLIM many moons ago - Sorry My Bad, I was working from my 'obviously flawed' memory.
As ConsoleKit is a dependency of SLIM I'll obviously need to keep it around for the time being. One final question - Do I need to do anything more with it than just have it installed on the system?

[SOLVED] systemd and blacklisting modules

Hi,
I recently found out about the 'systemctl status foo.service'-cmd and I was finally able to see why the systemd-modules-load-service was failing on my laptop.
It complains it cannot find service-files for 'blacklist nouveau' and other modules I have blacklisted. The wiki mentions blacklisting is done the same for systemd as for sysV-init, i.e. through a simple 'blacklist <modulename>' inside a .conf-file residing in either:
/etc/modprobe.d/ or
/etc/modules-load.d/
What am I doing wrong?
Last edited by zenlord (2012-08-24 19:38:38)

tomegun wrote:The .conf file must be in /etc/modprobe.d and not in /etc/modules-load.d.
OK, that's the one. I was mistaken to think that both directories had the same functionality.
THX!
Marking as solved.
Last edited by zenlord (2012-08-24 19:38:11)

[SOLVED] Systemd and laptop-mode-tools frequency scaling

Hi all.
After a long time with no arch updates (november 2011) for various reasons, I decided to reinstall Arch from point 0 on my Clevo laptop.
I was pleased to see nothing went bad, all is now set like I want. I installed systemd yesterday. All very straightforward for me, I only have a problem with CPU frequency scaling plus some minor glitches.
Before systemd, everything went fine. Ondemand governor, set up like I wanted.
Now when on AC the system uses ondemand, but when on battery it uses the conservative governor. What's more, it does not go over 1.6GHz (2.54GHz max).
Here are some infos about it:
[adriano@M735T ~] cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 2.53 GHz
available frequency steps: 2.53 GHz, 2.53 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
boost state support:
Supported: yes
Active: yes
[yes this is all come out of the cpupower command, no mention of CPU 1. Is this normal?]
Of course LMT is set up correctly
CONTROL_CPU_FREQUENCY="1"
BATT_CPU_MAXFREQ=fastest
BATT_CPU_MINFREQ=slowest
BATT_CPU_GOVERNOR=ondemand
BATT_CPU_IGNORE_NICE_LOAD=1
LM_AC_CPU_MAXFREQ=fastest
LM_AC_CPU_MINFREQ=slowest
LM_AC_CPU_GOVERNOR=ondemand
LM_AC_CPU_IGNORE_NICE_LOAD=1
NOLM_AC_CPU_MAXFREQ=fastest
NOLM_AC_CPU_MINFREQ=slowest
NOLM_AC_CPU_GOVERNOR=ondemand
NOLM_AC_CPU_IGNORE_NICE_LOAD=0
[adriano@M735T ~] sudo systemctl status laptop-mode-tools.service
laptop-mode-tools.service - Laptop Power Saving Tools
Loaded: loaded (/usr/lib/systemd/system/laptop-mode-tools.service; enabled)
Active: active (exited) since Sun, 02 Sep 2012 17:03:45 +0200; 4h 34min ago
Main PID: 367 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/laptop-mode-tools.service
Sep 02 17:03:43 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
Sep 02 17:03:44 M735T laptop_mode[367]: /usr/sbin/laptop_mode: line 198: /dev/fd/1: No such device or address
I wonder why LMT status is "exited"
OK bin that, I just now see something is wrong. I said it used conservative, but I'm on battery and it now says ondemand (still 1.6GHz max). However it seems it does so casually.
ACPI:
[adriano@M735T ~] acpi
Battery 0: Discharging, 53%, rate information unavailable
This may be (?) or may not be linked with nother problem I have: when unplugging the AC the KDE battery monitor does not update. It says AC is plugged and it will not activate power saving features (screen dimming, suspend...)
Note that this battery monitor problem occurred even before systemd, so it should not be linked to the above problem. However I'm not 100% sure the above problems did not occur before installing systemd since I only had the system up and running for a comple of days. I seem to recall I checked and it worked fine.
Any idea why all this happens?
Last edited by OdinEidolon (2012-11-20 08:56:31)

Ok rebooted and this is the output of the pm-powersave log file:
(AC IN, no battery)
(pastebin)
http://pastebin.com/Kf2Lx7UQ
If I grep cpupower:
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower true:
Setting cpupower frequency governor to conservative...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower true: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
Running hook /usr/lib/pm-utils/power.d/cpupower false:
Setting cpupower frequency governor to ondemand...Setting cpu: 0
/usr/lib/pm-utils/power.d/cpupower false: success.
right now:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing as it should (battery is disconnected)
3) acpi -a reports AC in as it should
4) all KDE stuff works OK
Now I plug the battery in:
1) cpupower reports ondemand and 2.54GHz (right)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports AC in as it should
4) KDE battery monitor reports no battery in, as signaled by acpi
5) if performing acpi_listen ,it reports nothing interesting
Now I unplug AC:
Absolutely nothing changes (not even in the log file) but:
1) cpupower reports ondemand and 1.6GHz (wrong)
2) acpi -bi reports nothing, which is wrong
3) acpi -a reports no AC as it should
4) KDE battery monitor reports no battery in, as signaled by acpi, but it also reports AC is inserted

[Solved] systemd and fstab with /var bind

Similar Messages

Maybe you are looking for