[SOLVED] Mounting /tmp as a ramdisk with systemd

Hi, how would one go about setting up /tmp to be a ramdisk when using systemd? (I'm entirely new to systemd, but since Arch is switching to it I guess I need to learn it.) With rc.sysinit it was simple; I just added a call to "mount" early on in the script.
Last edited by jlindgren (2012-08-28 00:16:56)

jlindgren wrote:There was some reason I was mounting it earlier on than it would have been from /etc/fstab with initscripts -- but I can't remember what that reason was. Possibly it would not even matter for systemd; anyway, I'll try it. Thanks.
If you really need it early you should add a hook for the initrd and rebuild it. (similar to the usr-hook I think)
Last edited by progandy (2012-08-27 23:16:31)

Similar Messages

[solved] Setting up a "persistent" ramdisk with systemd

I have been doing much thinking in terms of using a ramdisk (tmpfs) to mitigate, or rather postpone SSD write limit issues as well as to enhance system performance. After following the steps described in the Ramdisk wiki page to no avail, I realized I have a systemd setup. I have also found another topic describing how to "hack" init scripts into the systemd build but I am not sure this is the "right" (or most elegant) way. Essentially I would like to move/copy several folders to a ramdisk and have its contents written back to disk after system suspend/shutdown. Just general guidelines would suffice!
(1) How should I go about setting up a "persistent" ramdisk with systemd? How would I setup "before" and "after" hooks?
(2) From what I have gathered so far, it appears that for the above, using rsync rather than cp would be a more efficient way to write ramdisk contents to disk. Is this true?
(3) The example described in the Ramdisk wiki page loads pacman cache and lib into a ramdisk. How about completely putting /var to a ramdisk?
(4) Will doing what I have described above (including /var) possibly leave my system in an inconsistent state?
I am trying to get this running on a computer with 8 GB of RAM on which memory usage rarely goes above 2 GB. I am not too worried about power failures as what I intend to put on the ramdisk is not mission critical (with the possible exception of /var).
I apologize in advance if I posted my concerns in the wrong subforum as I am both a Linux rookie and an Arch noob; I have also tried using the search function but I may have formulated my query improperly (the answers seemed irrelevant!) Thanks in advance for your time and please let me know if I have omitted important details.
Last edited by ndejay (2012-10-31 13:50:02)

#create 'ramdisksave' directory using terminal
mkdir /home/ramdisksave
#edit grub config or custom_40. This allocates max ram for ramdisks
kernel /vmlinuz ramdisk_size=2048000
#edit rc.local add these lines to create & mount ramdisk at boot
mke2fs -t ext2 /dev/ram1 2048000
mount /dev/ram1 /home/ramdisksave
#copies 'ramdisksave' contents to ramdisk save as *.sh make exe!
cp -a /home/ramdisksave/. /mnt/ram1
#saves ramdisk contents to ramdisksave folder save as *.sh make exe!
cp -a /mnt/ram1/. /home/ramdisksave/
#deletes ramdisk contents save as *.sh make exe!
cd /mnt && rm -rf ram1/*
#deletes ramdisksave contents save as *.sh make exe! DANGEROUS!!
cd /home && rm -rf ramdisksave/*
for safety better to create ramdisksave on another partition. Scripts can be crontabbed, can add tar compression options to save space, use rsync to copy only new etc etc.......script lines can be added to r.sysinit for startup and rc.shutdown for load and save at startup and shutdown.
Last edited by st.emsee (2013-06-22 11:23:44)

[SOLVED] Mounting securityfs Without Error Messages from systemd

Hello,
I noticed that securityfs is not automatically mounted to /sys/kernel/security on my system, and I want to use it for my TOMOYO setup. So I placed this line in my /etc/fstab:
securityfs /sys/kernel/security securityfs rw,relatime 0 0
However, at startup, I receive an error saying that I gave bad syntax or options. It suggests I check out the system log for any useful info. But there is nothing special listed there around the area where partitions are being remounted:
[ 9.768839] EXT4-fs (sda5): re-mounted. Opts: (null)
[ 9.815244] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: stripe=4
[ 9.859178] scsi 7:0:0:0: Direct-Access SAMSUNG HD103SI PQ: 0 ANSI: 2 CCS
[ 9.860225] sd 7:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 9.860931] sd 7:0:0:0: [sdc] Write Protect is off
[ 9.860935] sd 7:0:0:0: [sdc] Mode Sense: 28 00 00 00
[ 9.861771] sd 7:0:0:0: [sdc] No Caching mode page present
[ 9.861801] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 9.864702] sd 7:0:0:0: [sdc] No Caching mode page present
[ 9.864791] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 9.865511] sdc: sdc1
[ 9.868391] sd 7:0:0:0: [sdc] No Caching mode page present
[ 9.868480] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 9.868566] sd 7:0:0:0: [sdc] Attached SCSI disk
[ 9.885457] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[ 9.927526] Adding 3905532k swap on /dev/sda8. Priority:-1 extents:1 across:3905532k
Even more, securityfs shows up in /etc/mtab like a champ, as if nothing bad had happened. It works just fine with all of the relevant TOMOYO commands, as well. Here is my mount output:
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1948936k,nr_inodes=487234,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda5 on / type ext4 (rw,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sda6 on /boot type ext4 (rw,nosuid,nodev,noexec,relatime,stripe=4,data=ordered)
/dev/sda7 on /home type ext4 (rw,nosuid,nodev,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
binfmt on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
But errors on startup are less than ideal, and they are usually not for nothing. I assume there must be a more clean way to take care of this other than fstab. I attemped to look into using initcpio (since it takes care of proc, sys, etc.), but I am starting to beleive I shouln't mess with that either.
Any thoughts?
Last edited by novembrine (2012-11-27 09:16:33)

Uh, security reasons? I don't follow...
If that's your /proc/self/mounts, then you aren't actually booting with systemd. You would be seeing a large number of cgroup mounts and, among other things, securityfs would be mounted for you. example...
rootfs / rootfs rw 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
dev /dev devtmpfs rw,nosuid,relatime,size=6149824k,nr_inodes=1537456,mode=755 0 0
run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
/dev/sda2 / ext4 rw,noatime,discard,data=ordered 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_prio 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
systemd-1 /home autofs rw,relatime,fd=32,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
systemd-1 /mnt/Gluttony autofs rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
systemd-1 /mnt/Haven autofs rw,relatime,fd=34,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,size=512000k 0 0
/dev/sda1 /boot ext3 rw,nodev,noexec,noatime,data=ordered 0 0
/dev/sdb1 /home ext4 rw,relatime,data=ordered 0 0
/dev/sdb2 /mnt/Gluttony ext4 rw,nodev,noatime,data=ordered 0 0
/dev/sdc1 /mnt/Haven ext4 rw,nodev,noatime,data=ordered 0 0
/dev/sdc1 /srv/nfs/vmbin ext4 rw,nodev,noatime,data=ordered 0 0
/dev/sdc1 /srv/nfs/pkgs ext4 rw,nodev,noatime,data=ordered 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
note that securityfs doesn't show up here because it's not in my kernel.
Last edited by falconindy (2012-11-27 05:59:17)

[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] How to restart all services with systemd?

I had the habit of restarting all daemons after an upgrade so to make sure the newest libraries, configuration files etc were loaded. I did that with a shell script that restarted the daemons in order which they were listed in rc.conf. With systemd I could do something similar by first getting a list of running services and ordering a 'systemcrl restart <servicename>' for each. But since systemd keeps track of dependencies I wonder if that would be the way to do it. Also I would need to filter out 'one shot' type services that are only needed on bootup.
<edit>restart instead of reload</edit>
<edit>solved it with a little script</edit>
Last edited by rwd (2012-11-27 21:02:02)

I think that's what systemctl snapshot does.
snapshot [NAME]
Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If none is specified an automatic snapshot name is generated. In either case, the snapshot name used is printed to STDOUT, unless --quiet is specified.
A snapshot refers to a saved state of the systemd manager. It is implemented itself as a unit that is generated dynamically with this command and has dependencies on all units active at the time. At a later time the user may return to this state by using the isolate command on the snapshot unit.
Snapshots are only useful for saving and restoring which units are running or are stopped, they do not save/restore any other state. Snapshots are dynamic and lost on reboot.
Then, isolate emergency.target or rescue target and switch to the snapshot.

[solved] Cannot activate wake on lan with systemd

I have activated successfully wake on lan with systemd, following these guidelines :
https://wiki.archlinux.org/index.php/Wol#With_systemd
My [email protected] is:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/ethtool -s %i wol g
Type=oneshot
[Install]
WantedBy=multi-user.target
It worked nicely until I recently had to reinstall my server (following a disk replacement). Since then systemd fails to activate wake on lan.
Output from systemctl status wol@enp0s4 :
● [email protected] - Wake-on-LAN for enp0s4
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead) since ven. 2014-07-25 11:21:28 CEST; 23min ago
Process: 181 ExecStart=/usr/bin/ethtool -s %i wol g (code=exited, status=0/SUCCESS)
Main PID: 181 (code=exited, status=0/SUCCESS)
Output from ethtool enp0s4|grep "Wake" :
Supports Wake-on: pg
Wake-on: d
If I explicitly start the service with systemctl start wol@enp0s4, then ethtool enp0s4|grep "Wake" shows:
Supports Wake-on: pg
Wake-on: g
My guess is that the service does not start at the correct timing at boot.
I have also tried wol-systemd package from the AUR without success.
Last edited by elb (2014-07-25 15:02:21)

After a fiew tries and reading docs, I found that replacing network.target with multi-user.target in [email protected] seems to work for me.

[SOLVED]Mounting usb drives "not authorized" with thunar-volman (XFCE)

Hi,
I'm new to Arch (even though I must be approximately at my 15th try at installing it properly) and I have a problem with thunar-volman.
Whenever I log in as user, and try to mount a usb drive with thunar, let's say I want to plug a drive labeled Ext3_8Go, I get the same message in a pop-up window : "Failed to mount Ext3_8Go (or anything close, not in English in the text), not authorized (that part is in English)"
My install is :
- net install
- partitions : 9Go for /, no swap, no separate /home
- packages : base and base-devel. The only modifications in the package list is that I remove ppp, pcmciautils, and xfsprogs.
- config : at the install stage I only modify rc.conf to change LOCALE and HOSTNAME, and pacman's mirrorlist to allow all French mirrors in addition to the one at the top.
When the usb installation is over, I run this script :
"installation_xfce.sh" (there may be some errors left, I modify this script as I learn) :
#!/bin/bash
# expected environment : freshly installed archlinux, login : root.
echo "Are you connected to internet ? If not, please Ctrl+C and reload this script when connected"
echo "Otherwise, press ENTER to continue installation"
read var_dummy
echo "Creation of the user : please type in your user name :"
read var_username
useradd -u 1000 -g users -G audio,lp,storage,optical,video,wheel,games,power,network -d /home/$var_username/ -s /bin/bash -m $var_username
echo "You will now be asked to create the password for this user:"
passwd $var_username
# Add servers for pacman to find packages
cat >> /etc/pacman.conf << EOF
[multilib]
Include = /etc/pacman.d/mirrorlist
[archlinuxfr]
Server = http://repo.archlinux.fr/\$arch
[catalyst]
Server = http://catalyst.apocalypsus.net/repo/catalyst/\$arch
EOF
# Install packages
pacman -Syyu
pacman -S acpi acpid alsa-oss alsa-plugins alsa-utils catalyst catalyst-utils cpufrequtils cups dbus gstreamer0.10-base-plugins iptables laptop-mode-tools mesa net-tools netcfg ntp pm-utils rfkill rsync sudo ttf-dejavu vim wireless_tools xf86-input-evdev xorg-server xorg-utils xorg-xinit xorg-xinput yaourt conky gamin gnome-icon-theme gnome-keyring gvfs-afc network-manager-applet networkmanager slim slim-themes archlinux-themes-slim hicolor-icon-theme xfce4 xfce4-goodies
# If pacman failed, better stop the script here, and wait for a network connection
if [[ $?!=0 ]]
then
echo : failed to install packages - check your network connection, or review script
exit 1
fi
# Fix sound issue
cat > /home/$var_username/.asoundrc << EOF
pcm.!default{
type hw
card 1
device 0
ctl.!default{
type hw
card 1
device 0
EOF
chown $var_username:users /home/$var_username/.asoundrc
# Configure video settings for X to use Catalyst
if [[ ! -e /etc/X11/xorg.conf.d ]]
then
mkdir /etc/X11/xorg.conf.d
fi
cat > /etc/X11/xorg.conf.d/20-fglrx.conf << EOF
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
EndSection
EOF
sed -e 's/top_left/bottom_right/' -e '/alignment/i\double_buffer yes' -e '/CPU Usage/a\${color lightgrey}Temperatures:' -e '/CPU Usage/a\ CPU:$color ${hwmon 0 temp 1}°C' </etc/conky/conky.conf >/home/$var_username/.conkyrc
chown $var_username:users /home/$var_username/.conkyrc
# Install clickpad support
yaourt -S xf86-input-synaptics-clickpad
# Add french keyboard to X
sed '/MatchIsKeyboard/a\\tOption "XkbLayout" "fr"' </etc/X11/xorg.conf.d/10-evdev.conf >/etc/X11/xorg.conf.d/10-evdev.conf.new
mv -f /etc/X11/xorg.conf.d/10-evdev.conf.new /etc/X11/xorg.conf.d/10-evdev.conf
# Add new daemons, remove old ones, disable hwclock and remove netfs since I don't use it. add it if you need it
sed '/DAEMONS=/c\DAEMONS=(!hwclock dbus syslog-ng networkmanager laptop-mode acpid @alsa @cupsd @cpufrequtils ntpd crond)' </etc/rc.conf >/etc/rc.conf.new
mv -f /etc/rc.conf.new /etc/rc.conf
# Slim login manager ; change theme
mv /usr/share/slim/themes/archlinux-darch-grey /tmp/
mv /usr/share/slim/themes/default /tmp/
rm -r /usr/share/slim/themes/*
mv /tmp/archlinux-darch-grey /usr/share/slim/themes
mv /tmp/default /usr/share/slim/themes
sed '/^current_theme/c\current_theme archlinux-darch-grey' </etc/slim.conf >/etc/slim.conf
# XFCE login, and thunar launched as a daemon
sed '/^# exec/c\' </etc/skel/.xinitrc >/tmp/.xinitrc
sed '/^# .../c\' </tmp/.xinitrc >/home/$var_username/.xinitrc
cat >> /home/$var_username/.xinitrc << EOF
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc
# Boot to runlevel 5 now, and run slim then
sed -e 's/id:3/#id:3/' -e 's/#id:5/id:5/' -e 's|x:5:respawn:/usr/bin/xdm|#x:5:respawn:/usr/bin/xdm|' -e 's|#x:5:respawn:/usr/bin/slim|x:5:respawn:/usr/bin/slim|' </etc/inittab >/etc/inittab.new
mv -f /etc/inittab.new /etc/inittab
# Add colored prompt to user and root
sed '/^PS1/c\' </etc/skel/.bashrc >/root/.bashrc
cat >> /root/.bashrc << EOF
PS1='\[\e[0;32m\]\u@\h\[\e[m\] \[\e[0;35m\]\w\[\e[m\] \[\e[m\] \[\e[0;32m\]\t -\[\e[m\] \[\e[1;31m\]\$ \[\e[m\] '
EOF
cp /root/.bashrc /home/$var_username/.bashrc
chown $var_username:users /home/$var_username/.bashrc
# How does one do that automatically ?
# Manually add user to sudoers
EDITOR="vim" visudo
# Reboot, because it's quick and I'm too lazy to learn how to start all the daemons and others.
reboot
I can mount as a user, no password asked, with :
udisks --mount /dev/sdb2
but the GUI method tells me "not authorized".
"groups user" outputs :
lp wheel games network video audio optical storage power users
the command "ck-list-sessions" outputs :
Session2:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-08-15T08:56:03.716103Z'
login-session-id = '1'
Session1:
unix-user = '1000'
realname = ''
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0.0'
x11-display-device = ''
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-08-15T08:56:03.573029Z'
login-session-id = '1'
For those who don't have time to read the installation script, DBUS is in the DAEMONS list of rc.conf, and .xinitrc launches : exec ck-launch-session startxfce4
Any idea ?
Last edited by choubbi (2011-08-15 15:05:04)

Thanks a lot !
That worked !
I stumbled across this part of the wiki several times before, but didn't really understand so I had not tried.
If anyone's interested in the script, here's the corrected version :
#!/bin/bash
# expected environment : freshly installed archlinux, login : root.
echo "Are you connected to internet ? If not, please Ctrl+C and reload this script when connected"
echo "Otherwise, press ENTER to continue installation"
read var_dummy
echo "Creation of the user : please type in your user name :"
read var_username
useradd -u 1000 -g users -G audio,lp,storage,optical,video,wheel,games,power,network -d /home/$var_username/ -s /bin/bash -m $var_username
echo "You will now be asked to create the password for this user:"
passwd $var_username
# Add servers for pacman to find packages
cat >> /etc/pacman.conf << EOF
[multilib]
Include = /etc/pacman.d/mirrorlist
[archlinuxfr]
Server = http://repo.archlinux.fr/\$arch
[catalyst]
Server = http://catalyst.apocalypsus.net/repo/catalyst/\$arch
EOF
# Install packages
pacman -Syyu
pacman -S acpi acpid alsa-oss alsa-plugins alsa-utils catalyst catalyst-utils cpufrequtils cups dbus gstreamer0.10-base-plugins iptables laptop-mode-tools mesa net-tools netcfg ntp pm-utils rfkill rsync sudo ttf-dejavu vim wireless_tools xf86-input-evdev xorg-server xorg-utils xorg-xinit xorg-xinput yaourt conky gamin gnome-icon-theme gnome-keyring gvfs-afc network-manager-applet networkmanager slim slim-themes archlinux-themes-slim hicolor-icon-theme xfce4 xfce4-goodies
# If pacman failed, better stop the script here, and wait for a network connection
if [[ $?!=0 ]]
then
echo : failed to install packages - check your network connection, or review script
exit 1
fi
# Fix sound issue
cat > /home/$var_username/.asoundrc << EOF
pcm.!default{
type hw
card 1
device 0
ctl.!default{
type hw
card 1
device 0
EOF
chown $var_username:users /home/$var_username/.asoundrc
# Configure video settings for X to use Catalyst
if [[ ! -e /etc/X11/xorg.conf.d ]]
then
mkdir /etc/X11/xorg.conf.d
fi
cat > /etc/X11/xorg.conf.d/20-fglrx.conf << EOF
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
EndSection
EOF
sed -e 's/top_left/bottom_right/' -e '/alignment/i\double_buffer yes' -e '/CPU Usage/a\${color lightgrey}Temperatures:' -e '/CPU Usage/a\ CPU:$color ${hwmon 0 temp 1}°C' </etc/conky/conky.conf >/home/$var_username/.conkyrc
chown $var_username:users /home/$var_username/.conkyrc
# Install clickpad support
yaourt -S xf86-input-synaptics-clickpad
# Add french keyboard to X
sed '/MatchIsKeyboard/a\\tOption "XkbLayout" "fr"' </etc/X11/xorg.conf.d/10-evdev.conf >/etc/X11/xorg.conf.d/10-evdev.conf.new
mv -f /etc/X11/xorg.conf.d/10-evdev.conf.new /etc/X11/xorg.conf.d/10-evdev.conf
# Add new daemons, remove old ones, disable hwclock and remove netfs since I don't use it. add it if you need it
sed '/DAEMONS=/c\DAEMONS=(!hwclock dbus syslog-ng networkmanager laptop-mode acpid @alsa @cupsd @cpufrequtils ntpd crond)' </etc/rc.conf >/etc/rc.conf.new
mv -f /etc/rc.conf.new /etc/rc.conf
# Slim login manager ; change theme
mv /usr/share/slim/themes/archlinux-darch-grey /tmp/
mv /usr/share/slim/themes/default /tmp/
rm -r /usr/share/slim/themes/*
mv /tmp/archlinux-darch-grey /usr/share/slim/themes
mv /tmp/default /usr/share/slim/themes
sed '/^current_theme/c\current_theme archlinux-darch-grey' </etc/slim.conf >/etc/slim.conf
# XFCE login, and thunar launched as a daemon (note that the part with 'if [ -d /etc/X11/xinit/xinitrc.d ]" is not present, to avoid mounting problems when logged as regular user)
cat > /home/$var_username/.xinitrc << EOF
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc
# Boot to runlevel 5 now, and run slim then
sed -e 's/id:3/#id:3/' -e 's/#id:5/id:5/' -e 's|x:5:respawn:/usr/bin/xdm|#x:5:respawn:/usr/bin/xdm|' -e 's|#x:5:respawn:/usr/bin/slim|x:5:respawn:/usr/bin/slim|' </etc/inittab >/etc/inittab.new
mv -f /etc/inittab.new /etc/inittab
# Add colored prompt to user and root
sed '/^PS1/c\' </etc/skel/.bashrc >/root/.bashrc
cat >> /root/.bashrc << EOF
PS1='\[\e[0;32m\]\u@\h\[\e[m\] \[\e[0;35m\]\w\[\e[m\] \[\e[m\] \[\e[0;32m\]\t -\[\e[m\] \[\e[1;31m\]\$ \[\e[m\] '
EOF
cp /root/.bashrc /home/$var_username/.bashrc
chown $var_username:users /home/$var_username/.bashrc
# How does one do that automatically ?
# Manually add user to sudoers
EDITOR="vim" visudo
# Reboot, because it's quick and I'm too lazy to learn how to start all the daemons and others.
reboot
The important part of the script to solve the problem is :
cat > /home/$var_username/.xinitrc << EOF
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc

[SOLVED] Mounting /tmp as tmpfs does not work?

Hi,
running arch since a few days now, and began a bit of tweaking.
I read, mounting the /tmp dir as a tmpfs adding the following line to my /etc/fstab should slightly increase performance. (plus removing the old /tmp mount rule)
none /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0
I have conky running showing my ram usage. Shouldn't the numbers increase if I copy something to the /tmp directory? I copied a large file to the dir. but nothing happened to the ram usage.
Thank you in advance, Peter
Last edited by phoenigs (2010-09-05 19:08:20)

Hi again,
Here the outputs of the two commands:
[peter@phlap|~]$ mount
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=493581,mode=755)
/dev/disk/by-uuid/4afd9796-b899-47a8-a4e0-04d70209a635 on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw)
shm on /dev/shm type tmpfs (rw,nosuid,nodev)
/dev/sda4 on /home type ext4 (rw)
/dev/sda1 on /boot type ext2 (rw)
none on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=1000M,mode=1777)
[peter@phlap|~]$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 208K 9.8M 3% /dev
/dev/disk/by-uuid/4afd9796-b899-47a8-a4e0-04d70209a635
39G 3.4G 34G 10% /
shm 1.9G 2.1M 1.9G 1% /dev/shm
/dev/sda4 104G 1.1G 98G 2% /home
/dev/sda1 99M 16M 79M 17% /boot
none 1000M 661M 340M 67% /tmp
(I know the / partition is chosen a bit too large)
But here is another output:
[peter@phlap|tmp]$ free -m
total used free shared buffers cached
Mem: 3858 1965 1892 0 28 1605
-/+ buffers/cache: 330 3527
Swap: 4502 0 4502
As you can see, the mounting works properly. I have copied a 600mb file to /tmp, and it still says 330mb free ram. Or does the tmpfs count as "cached"?
I just want the "proof" that my /tmp directory is in the ram now
Last edited by phoenigs (2010-09-04 22:54:13)

[SOLVED] Can not shutdown/restart from KDE with systemd

Hello,
Recently, following I switched to a pure systemd setup. The process was simple and most things worked "right out of the bpx". However, I can not shutdown or restart from KDE!
Let's say that I do the 3 finger salute (ALT-CTRL-DEL) and select "Turn off computer" what I get is KDE shutting down, but then I will only get a console (TTY) login prompt. Pressing ALT-CTRL-DEL then will trigger a reboot. I can also login and use "systemctl poweroff". However, I don't understand why it doesn't work straight from KDE.
Are there some packages I must install? Are there some systemd services that I must enable? What other relevant info should I include in this post?
Active units :
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
sys-devi...d-card0.device loaded active plugged MCP79 High Definition Audio
sys-devi...da-sda1.device loaded active plugged ST9500420ASG
sys-devi...da-sda2.device loaded active plugged ST9500420ASG
sys-devi...da-sda3.device loaded active plugged ST9500420ASG
sys-devi...da-sda4.device loaded active plugged ST9500420ASG
sys-devi...da-sda5.device loaded active plugged ST9500420ASG
sys-devi...da-sda6.device loaded active plugged ST9500420ASG
sys-devi...ock-sda.device loaded active plugged ST9500420ASG
sys-devi...et-eth0.device loaded active plugged RTL8111/8168B PCI Express Gigabit Ethernet controller
sys-devi...t-wlan0.device loaded active plugged AR928X Wireless Network Adapter (PCI-Express)
sys-devi...y-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-fuse.device loaded active plugged /sys/module/fuse
-.mount loaded active mounted /
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home.mount loaded active mounted /home
run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs
sys-fs-f...nections.mount loaded active mounted FUSE Control File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted /tmp
cups.path loaded active waiting CUPS Printer Service Spool
systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
bluetooth.service loaded active running Bluetooth service
colord-sane.service loaded active running Daemon for monitoring attached scanners and registering them with colord
colord.service loaded active running Manage, Install and Generate Color Profiles
console-...daemon.service loaded active running Console Manager
console-...-start.service loaded active exited Console System Startup Logging
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
kdm.service loaded active running K Display Manager
NetworkManager.service loaded active running Network Manager
sshd.service loaded active running OpenSSH Daemon
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-...s-load.service loaded active exited Load Kernel Modules
systemd-...unt-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...rigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...ssions.service loaded active exited Permit User Sessions
systemd-...-setup.service loaded active exited Setup Virtual Console
udisks2.service loaded active running Storage Daemon
upower.service loaded active running Daemon for power management
wpa_supplicant.service loaded active running WPA supplicant
cups.socket loaded active running CUPS Printing Service Sockets
dbus.socket loaded active running D-Bus System Message Bus Socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...control.socket loaded active listening udev Control Socket
systemd-...-kernel.socket loaded active running udev Kernel Socket
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
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
systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
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.
72 units listed. Pass --all to see inactive units, too.
Last edited by Prozzaks (2012-08-20 17:35:48)

Demon wrote:For me the system only halts, it does not poweroff. How I can solve this?
As bgc1954 said, there is also a symlink "/sbin/poweroff". Just edit the file "/usr/share/config/kdm/kdmrc", go to [shutdown] an replace the line "HaltCmd=/sbin/halt" with "HaltCmd=/sbin/poweroff".

[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] How to mount multi-device btrfs filesystem under systemd?

I am running full, native systemd. It always has an error during boot trying to mount my new, multi-device btrfs filesystem. There was no problem with mounting the filesystem when it resided on a single disk drive.
When it fails, it allows me to enter my root password and have a console. In this console, I can successfully mount the btrfs filesystem. Then boot continues normally, and then I can use the filesystem with no further problems, until the next reboot.
btrfs filesystem show /dev/sda4
failed to read /dev/sr0
Label: 'TimBTRFS' uuid: 317460bc-5b6a-4dac-acb8-7139dcbcff8b
Total devices 2 FS bytes used 31.67GB
devid 2 size 100.00GB used 2.00GB path /dev/sdb1
devid 1 size 100.00GB used 42.02GB path /dev/sda4
Btrfs Btrfs v0.19
I looked up btrfs in the wiki, and it says I have to run "btrfs device scan" before I can mount the filesystem. "This is the purpose of the btrfs mkinitcpio hook or the USEBTRFS variable in /etc/rc.conf" I do not have an rc.conf. I do not know how to do this with systemd. What do I need to do to resolve this?
Tim
Last edited by ratcheer (2012-09-06 12:12:24)

I added the btrfs hook as per the previous post. I ran "mkinitcpio -p linux". I ran grub-mkconfig. I rebooted and got the exact same problem. I did see the message early in the boot output that the btrfs hook was executed.
Here are the error messages:
[ 203.780864] device label TimBTRFS devid 1 transid 140 /dev/sda4
[ 203.781779] btrfs: disk space caching is enabled
[ 203.790133] btrfs: failed to read chunk tree on sda4
[ 203.790973] btrfs: open_ctree failed
Again, in the root console, I simply mounted the filesystem ("mount -t btrfs /dev/sda4 /btrfs"), typed Ctrl-d, and the bootup continued normally and successfully.
I need help, please.
Tim

[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

Howto suspend with systemd [SOLVED]

Hi All,
I have converted my machines to full systemd including some laptops. ... and am on the whole, very happy with systemd ..
I notice my daughter's laptop (a Samsung N70) sleeps and resumes just fine without any extra work from me ..
However, my Sony vaio laptop just reboots when I use the Gnome3 suspend menu item. Is there something else I can try to get it to suspend?
I presume the Gnome3 suspend is suspend and not hibernate to disk ..
NB: The samsung was installed from a fresh installation, where the Sony has been recently upgraded and converted to systemd.
Thanks,
B
Last edited by bmentink (2012-09-17 04:18:14)

First of all, don't presume things - establish the facts. I have no experience with Gnome, so my advice would be to see if 'systemctl suspend' works in a terminal. If it does, then you need to make sure that's what Gnome uses. If it doesn't you have a more fundamental issue, and the information provided by the systemd journal will help you solve it.

Getting sasc-ng to work properly with systemd service files [SOLVED]

This thread is intended for getting the following AUR packages to work with each other with systemd service scripts:
https://aur.archlinux.org/packages/open-sasc-ng-dkms/
https://aur.archlinux.org/packages/open-sasc-ng/
https://aur.archlinux.org/packages/oscam-svn/ (this is a related package as it must properly execute prior to sasc-ng)
So my server is now on a fresh Arch install with systemd. All is well (& very fast) except I cannot get sasc-ng to function with systemd service init files. Prior to systemd the system worked fine with the rc initscripts & was very stable with the following setup:
rc.local
/etc/rc.d/oscam start
sleep 15
/etc/rc.d/sasc-ng start
sleep 4
/etc/rc.d/mythbackend start
/etc/conf.d/sasc-ng.conf
SASCNG_ARGS="-j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget"
DVBLOOPBACK_ARGS="num_adapters=3"
LOGDIR="/home/mythtv/logs/"
CAMDIR="/etc/camdir"
/etc/camdir/cardclient.conf
camd35:localhost:15050:1/0000/0000:mythtv:mythtv
I'll leave out the oscam stuff as that loads fine and doesn't appear to be a part of the problem
I've tried this with the systemd service file that comes with the open-sasc-ng-dkms package and when it was not sucessful I tried a bunch of variants including using "Type=simple" ect. "Type=Forked" seems to be only option that actually tries to start the processes. I also "hardcoded" the service files for the 2 sasc-ng components to find a few issues with the EnvironmentFile variables. The log variable has been removed for now as this seems to cause a fatal error but the rest of the variables load fine now. I also tested spliting up the DVB loopback module from the sasc-ng binary but this also gives similar results as the following script stands now. Running them manually with systemctl start commands doesn't make a difference but that is not surprising. The service file I'm fiddling with now which I feel has the best potential become working is:
sasc-ng.service
[Unit]
Description=Sasc-ng
After=oscam.service
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/sasc-ng
ExecStartPre=/sbin/modprobe dvbloopback $DVBLOOPBACK_ARGS
TimeoutSec=2
ExecStart=/usr/sbin/sasc-ng -D $SASCNG_ARGS --cam-dir=$CAMDIR
TimeoutSec=4
[Install]
WantedBy=multi-user.target
Mythbackend always runs fine (even without DTV via sasc-ng) with the following mythbackend.service:
[Unit]
Description=MythTV_backend
After=sasc-ng.service
[Service]
Type=simple
Environment=MYTHCONFDIR=/etc/conf.d/mythbackend
Environment=HOME=/usr/share/mythtv
User=mythtv
ExecStart=/usr/bin/mythbackend --logpath /var/log/mythtv
[Install]
WantedBy=multi-user.target
oscam.service taken mostly from AUR package also seems fine. I added the TimeoutSec=15 to give time for oscam to load the SC and client protocol before moving on or else sasc-ng fails
Unit]
Description=An Open Source Conditional Access Module software
After=network.target
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/oscam
ExecStart=/usr/bin/oscam $OSCAM_ARGS
TimeoutSec=15
[Install]
WantedBy=multi-user.target
Below is the output of the systemctl status commands. Despite the noise in the sasc-ng binary status, it is the loopback module that is " inactive (dead)" and there are no virtual DVB devices being created:
[mythtv@server ~]$ sudo systemctl status oscam.service
oscam.service - An Open Source Conditional Access Module software
Loaded: loaded (/usr/lib/systemd/system/oscam.service; enabled)
Active: active (running) since Tue, 2012-11-27 21:10:17 CET; 1min 7s ago
Process: 338 ExecStart=/usr/bin/oscam $OSCAM_ARGS (code=exited, status=0/SUCCESS)
Main PID: 377 (oscam)
CGroup: name=systemd:/system/oscam.service
├ 377 /usr/bin/oscam -b -c /etc/oscam
└ 378 /usr/bin/oscam -b -c /etc/oscam
Nov 27 21:10:17 server systemd[1]: Started An Open Source Conditional Acces...e.
[mythtv@server ~]$ sudo systemctl status loopback.service
loopback.service - Sasc-ng DVB Loopback Module
Loaded: loaded (/etc/systemd/system/loopback.service; enabled)
Active: inactive (dead) since Tue, 2012-11-27 21:10:28 CET; 1min 27s ago
Process: 907 ExecStart=/sbin/modprobe dvbloopback num_adapters=3 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/loopback.service
Nov 27 21:10:28 server systemd[1]: Started Sasc-ng DVB Loopback Module.
[mythtv@server ~]$ sudo systemctl status sasc-ng.service
sasc-ng.service - Sasc-ng
Loaded: loaded (/etc/systemd/system/sasc-ng.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-27 21:10:47 CET; 1min 45s ago
Process: 913 ExecStart=/usr/sbin/sasc-ng -D -j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget --cam-dir=/etc/camdir -l /home/mythtv/logs/sasc-ng.log (code=exited, status=0/SUCCESS)
Main PID: 921 (code=exited, status=255)
CGroup: name=systemd:/system/sasc-ng.service
Nov 27 21:10:39 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc...ry
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.info] loading cardclien...nf
Nov 27 21:10:42 server sasc-ng[921]: [1062] Netwatcher thread started (pid=...6)
Nov 27 21:10:42 server sasc-ng[921]: [921] [general.error] no keys loaded f...m!
Nov 27 21:10:46 server sasc-ng[921]: [1098] SC housekeeper thread started (...2)
Nov 27 21:10:47 server sasc-ng[921]: [1062] Netwatcher thread ended (pid=92...6)
Nov 27 21:10:47 server systemd[1]: sasc-ng.service: main process exited, co.../a
Nov 27 21:10:47 server systemd[1]: Unit sasc-ng.service entered failed state
[mythtv@server ~]$ sudo systemctl status sasc-ng.service
sasc-ng.service - Sasc-ng
Loaded: loaded (/etc/systemd/system/sasc-ng.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-27 21:10:47 CET; 2min 9s ago
Process: 913 ExecStart=/usr/sbin/sasc-ng -D -j 0:3 -j 1:4 -j 2:5" -b 16M --sid-allpid --sid-nocache --cam-budget --cam-dir=/etc/camdir -l /home/mythtv/logs/sasc-ng.log (code=exited, status=0/SUCCESS)
Main PID: 921 (code=exited, status=255)
CGroup: name=systemd:/system/sasc-ng.service
Nov 27 21:10:39 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/smartcard.conf: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/cardslot.conf: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.error] failed open /etc/camdir/SoftCam.Key: No such file or directory
Nov 27 21:10:40 server sasc-ng[921]: [921] [general.info] loading cardclient config from /etc/camdir/cardclient.conf
Nov 27 21:10:42 server sasc-ng[921]: [1062] Netwatcher thread started (pid=921, tid=140074379712256)
Nov 27 21:10:42 server sasc-ng[921]: [921] [general.error] no keys loaded for softcam!
Nov 27 21:10:46 server sasc-ng[921]: [1098] SC housekeeper thread started (pid=921, tid=140074371319552)
Nov 27 21:10:47 server sasc-ng[921]: [1062] Netwatcher thread ended (pid=921, tid=140074379712256)
Nov 27 21:10:47 server systemd[1]: sasc-ng.service: main process exited, code=exited, status=255/n/a
Nov 27 21:10:47 server systemd[1]: Unit sasc-ng.service entered failed state
[mythtv@server ~]$
Any ideas?
Last edited by wdirksen (2012-12-10 19:54:43)

After some head scratching it seems to be all good now. Considering there have been no replies to this I've come to wonder if I might be the only one with this issue. I could get it working somewhat using service files but never ideal, ex. sasc-ng only using a few of the entitlements from oscam because it started too quick etc. Anyway this might help a few and I'm hoping the linux savvy who find what I'm writing here painfully newbie like or flawed will reply and educate me a bit if what's provided here needs some sharpening up:
1) Systemd was confusing the sasc-ng binary shorthand arguments with Linux init arguments and a few were misinterpreted if they were not nested into the environment specifiers. So the -l (log) was causing problems and -b (buffer) wasn't loading. To be safe I'm using only the sasc-ng longhand specifiers from now on (two "--" and more verbose) so that they can never be confused even if safely nested in an environment parameter. That means that /etc/conf.d/sasc-ng will also need to be changed to reflect this. I also decided to simplify the LOGFILE parameter to include the whole argument syntax.
2) Oscam.service needs to be initiated with oneshot and RemainAfterExit=yes to make sure the delay (15 seconds in my config) gets counted out before sasc-ng initiates.
[EDIT 12/12/2012: Initially I had a second TimeoutSec=2 after ExecStart in sasc-ng.service but this had no function. Turns out that it almost always does work without this delay but not always with my setup. Adding TimeoutSec=2 to mythbackend.service prior to ExecStart command does function and makes things init more consistant]
sasc-ng.service
[Unit]
Description=Sasc-ng
After=oscam.service
[Service]
Type=simple
EnvironmentFile=/etc/conf.d/sasc-ng
ExecStartPre=/sbin/modprobe dvbloopback $DVBLOOPBACK_ARGS
TimeoutSec=2
ExecStart=/usr/sbin/sasc-ng $SASCNG_ARGS --cam-dir $CAMDIR --log $LOGFILE
[Install]
WantedBy=multi-user.target
/etc/conf.d/sasc-ng
SASCNG_ARGS="--join 0:3 --join 1:4 --join 2:5 --buffer 16M --sid-allpid --sid-nocache --cam-budget"
DVBLOOPBACK_ARGS="num_adapters=3"
LOGFILE="/home/mythtv/logs/sasc-ng.log"
CAMDIR="/etc/camdir"
oscam.service
[Unit]
Description=An Open Source Conditional Access Module software
After=network.target
[Service]
Type=oneshot
EnvironmentFile=/etc/conf.d/oscam
ExecStart=/usr/bin/oscam $OSCAM_ARGS
TimeoutSec=15
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
mythbackend.service
[Unit]
Description=MythTV_backend
After=sasc-ng.service
[Service]
Type=simple
TimeoutSec=2
Environment=MYTHCONFDIR=/etc/conf.d/mythbackend
Environment=HOME=/usr/share/mythtv
User=mythtv
ExecStart=/usr/bin/mythbackend --logpath /var/log/mythtv
[Install]
WantedBy=multi-user.target
I will make the related changes to the open-sasc-ng AUR package which I currently maintain
Last edited by wdirksen (2012-12-23 14:40:43)

[SOLVED] Mounting /tmp as a ramdisk with systemd

Similar Messages

Maybe you are looking for