Command on boot - systemd tmpfile

Hi.
I have a laptop with ATI/Intel hybrid graphics. I am never using the ATI graphics when in Linux, and i simply want to turn the ATI card off on boot for battery-life. I used to do this in Ubuntu, simply by putting the command:
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
in /etc/rc.local
Now on Arch i have to go around making a tmpfile for systemd (by searching around it seems this is the "correct" way of doing this kind of stuff on boot), that will perform this action for me. However i find the syntax very difficult to understand, so if someone could help i would appreciate it. The tmpfile i have created so far (which ofcourse isnt working), is
/etc/tmpfiles.d/fix_graphics.conf
and contains the line
w /sys/kernel/debug/vgaswitcheroo/switch - - - - OFF
Could anyone give me a pointer to what could be wrong? And just for future reference: What would one do in order to run a general command or script (for doing stuff more complex than writing a line to a file etc.) as root on startup with systemd?
Thanks in Advance
Esben

Hi
According to the wiki you have to blacklist the radeon kernel module and then load it manually afterwards before executing the echo OFF >...
Also you've to enable debugfs in your fstab, all described in the wiki: https://wiki.archlinux.org/index.php/Hy … ons_So_Far
As for systemd I do this with a little script that is called by a custom service file, wiki: https://wiki.archlinux.org/index.php/Sy … vice_files
I've added some After=, Requires= and Before= "tags" to the service file to make sure it executes at a good time, (After/Requires=systemd-user-sessions.service, to not execute too early and cause a kernel panic and Before=xinit.service to start it before X is started)
Edit: Alternatively you could use acpi_call from AUR to switch off the DGP completely. However this requires some similar steps to execute on boot.
Last edited by rebootl (2012-12-19 14:20:10)

Similar Messages

Thousands of log entries for systemd-tmpfiles-clean.timer on boot

I'm running a 32 bit Arch install as a VMware ESXi 5.1 guest. Whenever the guest boots up, I get several thousand of the following entries in the system log:
Feb 18 12:49:01 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
The most recent boot had almost 20,000 entries within 5 seconds:
$ sudo journalctl -b | grep systemd-tmpfiles-clean.timer | wc -l
19693
$ sudo journalctl -b | grep systemd-tmpfiles-clean.timer | sed -n '1p;$p'
Feb 18 12:49:01 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Feb 18 12:49:06 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
I've pasted the entry into Google but have not come up with anything helpful.
I have disabled host-guest time sync:
$ vmware-toolbox-cmd timesync status
Disabled
There is a NTP daemon running that syncs time with a single windows server (which is also a guest on the same ESXi host).
As far as I'm aware there shouldn't be anything else playing with the time, but theres obviously something going on.
Can anyone please help me troubleshoot?

I've had the same problem and I don't know what's going wrong. But I have a workaround:
If you're booting into a graphical environment you can disable the vmtoolsd service
# systemctl disable vmtoolsd
and add the following line to your ~/.xinitrc:
vmware-user-suid-wrapper
The ~/.xinitrc will start the vmtoolsd service then.
This solved two problems for me:
1. No more messages like you posted in my log file.
2. The virtual machine shuts down promptly (see vmtoolsd not stopping)
Last edited by BertiBoeller (2013-03-14 13:40:21)

Adding simple commands to boot under systemd

now that the rc.xxxx files are gone, where is the preferred location for adding a simple command one might like to execute upon boot, e.g. "echo 'search somewhere.somedomain' >> /etc/resolv.conf"
obviously there are several ways to do this, i'm just wondering what a systemd expert would do.

djg1971 wrote:olive: please try to think a little more abstractly. it is not for you to judge whose one-line commands are good, not good, stupid, etc.
Please read my posts more carefully. I never said that there is no valid reason to run a custom command at boot, I was just pointed out, in a part of my post, that your example was not the best one; that's all and I do not understand why it seems to affect you so much.
Anyway, forget about the bad example. I have tried to answer your original question the best as I could: to run a custom command at boot, you have to write a .service or use a general rc-local script but apparently you do not like the answer. What do you want now? I do not know if I am an expert but I have read enough of systemd to know there is no real other way: systemd take in charge every program that is run at boot via .services (or .target, etc...) files. So this is the way you have to follow to run a custom command at boot. Writing a .service file is not that difficult, maybe easier than to write a custom rc.somewhat file. Just take one existing .service file, understand what there is in it and modify it.
The post of ewaller give a method to create tempory files, often used by .service files (or the programs they launches); I was not under the impression that is what you really want.
As for the benefits of systemd, there are a few advantages. Anyway it is not me that I have decided to switch to systemd and discussing lengthy of the advantages of disadvantages of it would lead to nowhere.
Last edited by olive (2013-02-25 22:09:21)

Systemd-tmpfiles-setup.service failure

Good evening friends.
I recently made a fresh install of arch linux on my pc and since the first boot up i get this error:
systemd-tmpfiles-setup.service failure
Failded to start create volatile files and directories
When i used "systemctl status" command on it, it said something about unkwnon groups in usr/lib/... somewhere, i can't remember all of it, because after i rebooted and tried the same command, it only said that the process failed, without giving much on details.
What might be the problem here?
Last edited by NotaName (2014-09-14 17:42:37)

falconindy wrote:
Just a guess, but I think you might have some unknown groups in usr/lib/... somewhere.
You'll really need to try harder to get the logs. They're still in the journal.
Thanks for the answer.
Well, i'm still working on the log finding part, as i'm not sure where they are supposed to be. I checked the /var/log folder files, but it seems that they are not readable/binary maybe?
P.S. Is this something that i might ignore if i don't find a way to fix it?
Last edited by NotaName (2014-09-14 19:36:47)

[SOLVED]systemd-tmpfiles-setup.service failure

Hi guys,
I just reinstalled arch with the following partitions:
[root@arch_vinnom vinnom]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BD3CA679-FA08-4F60-9BAD-B845DE9FF7EB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 BIOS
2 4096 52432895 25.0 GiB 8300 ROOT
3 52432896 53481471 512.0 MiB 8300 BOOT
4 53481472 74452991 10.0 GiB 8300 TMP
5 74452992 95424511 10.0 GiB 8300 VAR
6 95424512 602935295 242.0 GiB 8300 HOME
7 602935296 625142414 10.6 GiB 8200 SWAP
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime
Because of this, I'm always getting:
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Dom 2015-05-03 03:29:58 BRT; 27min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 278 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 278 (code=exited, status=1/FAILURE)
Then I tried to change '/tmp' to '/run/tmpfs', folder that I created for this, using tmpfs wiki as reference.
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/run/tmpfs
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/run/tmpfs
Type=tmpfs
Options=mode=1777,strictatime,nodev,nosuid,size=1536M
But the error persists. What I'm missing?
Last edited by vinnom (2015-05-03 16:51:38)

ooo wrote:Couldn't you just mask the tmp.mount service? (as mentioned in the wiki page you linked)
Then your /tmp partition would be mounted according to your fstab
Raynman wrote:
The tmp.mount generated from your fstab should override the tmp.mount in /usr/lib/systemd/system. You say
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
If that is true (could you show output of mount and your fstab?) that is worth investigating.
However, your original problem seems to be that systemd-tmpfiles-setup.service fails. If something is wrong with your mounts, that could be related, but it might very well be something else. Is there any more information in the journal to indicate why the service fails (maybe even mentioning a tmpfiles.d config file that is responsible)? Did you create any config files for tmpfiles.d yourself?
Sorry guys, I tried to be concise, but ended up that I didn't make myself clear.
My '/tmp' is mounting fine as it takes priority over systemd. In fact, what I wanted to say is that '/tmp' mounts fine, systemd tried to mount tmpfs at '/tmp' and fails and I want to point tmpfs to mount at '/run/tmpfs' which I created for this, but just editing '/usr/lib/systemd/system/tmp.mount' didn't solve.
As for journalctl, it repeats several times this message:
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Mai 02 22:43:32 arch_vinnom systemd[1]: Failed to start Create Volatile Files and Directories.
Mai 02 22:43:32 arch_vinnom systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service failed.
foutrelis wrote:
Depending on how your '/var' file system is created/mounted, you might need to enable ACL on it:
https://wiki.archlinux.org/index.php/Sy … rt_at_boot
hmm
I created my /var during arch installation, with mkfs.reiserfs.
Using
tune2fs -l /dev/sdXY | grep "Default mount options:"
To check if acl was already enabled, I got:
[root@arch_vinnom vinnom]# tune2fs -l /dev/sda5 | grep "Default mount options:"
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
Then I searched a bit and noted that reiserfs isn't compatible with acl =/
Last edited by vinnom (2015-05-03 15:12:18)

[SOLVED]systemd-tmpfiles-setup.service fails

Hi,
I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sal 2015-06-09 11:00:18 EEST; 38min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 228 (code=exited, status=1/FAILURE)
Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
Is this something that I should be concerned? I don't really know what this service supposed to do?
If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
Last edited by yasar11732 (2015-06-09 16:31:04)

Thanks,
I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
# UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0

High hard disk activity caused by systemd-tmpfile

Hi
I have home server PC running pure, console Archlinux on it 24/7. It works fine for about 3 years and still do, but after systemd transition I noticed that my server periodically runs systemd-tmpfile daemon which causes intensive and continuous hard disk activity.
My /etc/tmpfiles.d is empty, but here is the content of /usr/lib/tmpfiles.d folder:
-rw-r--r-- 1 root root 30 Sep 20 2012 apache.conf
-rw-r--r-- 1 root root 30 Jan 13 17:58 console.conf
-rw-r--r-- 1 root root 19 Jan 27 06:41 lastlog.conf
-rw-r--r-- 1 root root 1146 Jan 13 17:58 legacy.conf
-rw-r--r-- 1 root root 29 Feb 5 11:09 lirc.conf
-rw-r--r-- 1 root root 24 Mar 5 12:57 mpd.conf
-rw-r--r-- 1 root root 33 Feb 25 19:41 mysqld.conf
-rw-r--r-- 1 root root 27 Jan 27 09:09 nscd.conf
-rw-r--r-- 1 root root 51 Feb 25 17:32 samba.conf
-rw-r--r-- 1 root root 36 Oct 13 19:30 saslauthd.conf
-rw-r--r-- 1 root root 33 Dec 21 16:39 svnserve.conf
-rw-r--r-- 1 root root 736 Jan 13 17:58 systemd.conf
-rw-r--r-- 1 root root 449 Jan 13 17:58 tmp.conf
-rw-r--r-- 1 root root 30 Dec 13 15:24 uuidd.conf
-rw-r--r-- 1 root root 622 Jan 13 17:58 x11.conf
My question is how to know which *.conf file causes such a high HDD activity or how to resolve the problem at all?
Last edited by clovenhoof (2013-03-21 18:20:26)

Ok here is what get with "lsof -c systemd-tmpfile" during this activity:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-t 1069 root cwd DIR 8,3 4096 2 /
systemd-t 1069 root rtd DIR 8,3 4096 2 /
systemd-t 1069 root txt REG 8,3 59504 290840 /usr/bin/systemd-tmpfiles
systemd-t 1069 root mem REG 8,3 52144 262523 /usr/lib/libnss_files-2.17.so
systemd-t 1069 root mem REG 8,3 138206 262495 /usr/lib/libpthread-2.17.so
systemd-t 1069 root mem REG 8,3 18760 277530 /usr/lib/libattr.so.1.1.0
systemd-t 1069 root mem REG 8,3 2035539 262449 /usr/lib/libc-2.17.so
systemd-t 1069 root mem REG 8,3 31744 262453 /usr/lib/librt-2.17.so
systemd-t 1069 root mem REG 8,3 16776 299945 /usr/lib/libcap.so.2.22
systemd-t 1069 root mem REG 8,3 165436 262497 /usr/lib/ld-2.17.so
systemd-t 1069 root 0r CHR 1,3 0t0 6461 /dev/null
systemd-t 1069 root 1u unix 0xffff8801393df1c0 0t0 23160 socket
systemd-t 1069 root 2u unix 0xffff8801393df1c0 0t0 23160 socket
systemd-t 1069 root 3u unix 0xffff8801393dba80 0t0 23161 socket
systemd-t 1069 root 4r DIR 8,3 9482240 1970431 /var/tmp
systemd-t 1069 root 5r DIR 8,3 4096 793638 /var/tmp/systemd-private-G25Rag

[SOLVED] systemd-tmpfiles-clean takes a very long time to run

I've been having an issue for a while with systemd-tmpfiles-clean.service taking a very long time to run. I've tried to just ignore it, but it's really bothering me now.
Measuring by running:
# time systemd-tmpfiles --clean
systemd-tmpfiles --clean 11.63s user 110.37s system 10% cpu 19:00.67 total
I don't seem to have anything funky in any tmpfiles.d:
# ls /usr/lib/tmpfiles.d/* /run/tmpfiles.d/* /etc/tmpfiles.d/* | pacman -Qo -
ls: cannot access /etc/tmpfiles.d/*: No such file or directory
error: No package owns /run/tmpfiles.d/kmod.conf
/usr/lib/tmpfiles.d/gvfsd-fuse-tmpfiles.conf is owned by gvfs 1.20.1-2
/usr/lib/tmpfiles.d/lastlog.conf is owned by shadow 4.1.5.1-9
/usr/lib/tmpfiles.d/legacy.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/libvirt.conf is owned by libvirt 1.2.4-1
/usr/lib/tmpfiles.d/lighttpd.conf is owned by lighttpd 1.4.35-1
/usr/lib/tmpfiles.d/lirc.conf is owned by lirc-utils 1:0.9.0-71
/usr/lib/tmpfiles.d/mkinitcpio.conf is owned by mkinitcpio 17-1
/usr/lib/tmpfiles.d/nscd.conf is owned by glibc 2.19-4
/usr/lib/tmpfiles.d/postgresql.conf is owned by postgresql 9.3.4-1
/usr/lib/tmpfiles.d/samba.conf is owned by samba 4.1.7-1
/usr/lib/tmpfiles.d/slapd.conf is owned by openldap 2.4.39-1
/usr/lib/tmpfiles.d/sudo.conf is owned by sudo 1.8.10.p2-1
/usr/lib/tmpfiles.d/svnserve.conf is owned by subversion 1.8.8-1
/usr/lib/tmpfiles.d/systemd.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/systemd-nologin.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/tmp.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/uuidd.conf is owned by util-linux 2.24.1-6
/usr/lib/tmpfiles.d/x11.conf is owned by systemd 212-3
How do I debug why it is taking so long? I've looked in man 8 systemd-tmpfiles and on google, hoping to find some sort of --dubug option, but there seems to be none.
Is it some how possible to get a list of the directories that it looks at when it runs?
Anyone have any suggestions on how else to fix this.
Anyone else have this issue?
Thanks,
Gary
Last edited by garyvdm (2014-05-08 18:57:43)

Thank you very much falconindy. SYSTEMD_LOG_LEVEL=debug helped my find my issue.
The cause of the problem was thousands of directories in /var/tmp/ created by a test suite with a broken clean up method. systemd-tmpfiles-clean was recursing through these, but not deleting them.

Invalid command in boot strap mode

Hi All,
I am trying to install peoplesoft HRMS 9.1 with PT 8.51.
Firstly I encountered problems running grant.sql ,it showed that PSSTATUS, PSOPRDEFN, PSACCESSPRFL TABLE OR VIEW does not exist.(So i tried following "Using Data Mover, You can login in to the SYSTEM schema and EXPORT those tables (Using the 'EXPORT <RECORD>' instead of 'EXPORT *'). Then using Data Mover again, login to the SYSADM schema and IMPORT the data. NOTE: You will need two DMS scripts, one to export and one to import, as well as making sure you're using the right USER/PW combination" solution).
Secondly I can login to DATA MOVER using three combination of id's and psswds i.e system/oracle(original bootstrap mode id's) and PS/PS, SYSADM/SYSADM but the last two combinations also shows as bootstrap mode inside datamover.
Lastly i triesd to import the three tables from one schema to other by logging in to system/oracle as all three tables are present under this schema but when i run,
set log C:\REF0001_EXPORT.log;
set output C:\REF0001.dat;
export PSSTATUS;
It shows the below error in logs,
Invalid command in boot strap mode
Ended: Tue Jun 14 00:37:12 2011
Unsuccessful completion
Pls help!

Thanks Nicolas,
So now what do you advise me to do...Do i need to start a fresh from scratch??..I beleive half of the tables present r under SYSADM and rest half under SYSTEM..So is there anything which i can do to import those??

Systemd-tmpfiles and gvfs - permission denied

systemd-tmpfiles[2346]: stat(/run/user/1000/gvfs) failed: Permission denied
Can anyone tell me why this is in my journalctl ? Sometimes many times, depending on the application I use,
other times, once or twice in a 5 hour uptime.

same here with systemd. From log file:
localhost systemd-tmpfiles[12898]: stat(/run/user/1000/gvfs) failed: Permission denied
[gabx@magnolia:1000]$ ls -al
dr-x------ 2 gabx users 0 Aug 31 21:32 gvfs
[gabx@magnolia:1000]$ chmod -R u+w gvfs
[gabx@magnolia:1000]$ ls -al
dr-x------ 2 gabx users 0 Aug 31 21:32 gvfs
As you can see, can't even change permission for user gabx to write the directory.
EDIT:
[gabx@magnolia:~]$ systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; enabled)
Active: active (exited) since Fri, 31 Aug 2012 21:32:00 +0200; 46min ago
Docs: man:tmpfiles.d(5)
Process: 353 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
[gabx@magnolia:~]$ sudo systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; enabled)
Active: active (exited) since Fri, 31 Aug 2012 21:32:00 +0200; 47min ago
Docs: man:tmpfiles.d(5)
Process: 353 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
Following the above status, it seems everything is OK, so I am not sure this permission denied is really an issue.
Last edited by gabx (2012-08-31 23:31:01)

[SOLVED]Systemd Tmpfile Setup Service Fails

I'm not sure what version this began but I'm using systemd 185-1 and systemd-arch-units 20120606-4. Service just fails to start. Is this fixable?
└╼ $ systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: failed (Result: exit-code) since Fri, 22 Jun 2012 04:22:15 -0400; 36s ago
Docs: man:tmpfiles.d(5)
Process: 931 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
Last edited by Hspasta (2012-06-23 04:31:05)

swanson wrote:Check fstab and comment out the tmp there.
Did and didn't help.
WorMzy wrote:
Do you have any aur/custom-made packages that put *.conf files in /usr/lib/tmpfiles.d or /usr/local/lib/tmpfiles.d?
Does the system journal have any more information about the failure?
Hm...I have a lot of stuff in /usr/lib/tmpfiles.d/
└╼ $ ls /usr/lib/tmpfiles.d/
total 44K
-rw-r--r-- 1 root root 30 Jun 4 16:12 console.conf
-rw-r--r-- 1 root root 29 May 27 00:29 consolekit.conf
-rw-r--r-- 1 root root 74 Jun 6 19:02 initscripts.conf
-rw-r--r-- 1 root root 719 Jun 4 16:12 legacy.conf
-rw-r--r-- 1 root root 61 Jun 16 01:28 lvm2.conf
-rw-r--r-- 1 root root 24 Jun 1 00:04 mpd.conf
-rw-r--r-- 1 root root 27 Jun 9 03:29 nscd.conf
-rw-r--r-- 1 root root 30 Jun 9 01:41 openssh.conf
-rw-r--r-- 1 root root 729 Jun 4 16:12 systemd.conf
-rw-r--r-- 1 root root 449 Jun 4 16:12 tmp.conf
-rw-r--r-- 1 root root 622 Jun 4 16:12 x11.conf
I feel like something in my system is broken...

[Not solved]systemd-tmpfiles stat(/run/user/myuser/gvfs) failed: Perm

I get this error message since a couple of days and systemd-tmpfiles service is slow to start compared to before. I have no arch-units/initscripts anymore. I update everyday but I can see no updates that sticks out in pacman-log, on the day before this failure appeared. (systemd-tools was updated 3 days before this error)
Permissions;
/run/user
drwxr-xr-x 3 root root 60 7 jun 10.51 .
drwxr-xr-x 11 root root 340 7 jun 10.51 ..
drwx------ 3 myuser myuser 80 7 jun 10.51 myuser
/run/user/myuser
drwx------ 3 myuser myuser 80 7 jun 10.51 .
drwxr-xr-x 3 root root 60 7 jun 10.51 ..
dr-x------ 2 myuser myuser 0 7 jun 10.51 gvfs
lrwxrwxrwx 1 root root 17 7 jun 10.51 X11-display -> /tmp/.X11-unix/X0
/run/user/myuser/gvfs
dr-x------ 2 myuser myuser 0 7 jun 10.51 .
drwx------ 3 myuser myuser 80 7 jun 10.51 ..
EDIT: Now I've look at the files;
/usr/lib/tmpfiles.d
totalt 160K
drwxr-xr-x 2 root root 4,0K 2 jun 15.54 .
drwxr-xr-x 167 root root 128K 7 jun 07.34 ..
-rw-r--r-- 1 root root 30 1 jun 02.28 console.conf
-rw-r--r-- 1 root root 29 27 maj 06.29 consolekit.conf
-rw-r--r-- 1 root root 719 1 jun 02.28 legacy.conf
-rw-r--r-- 1 root root 729 1 jun 02.28 systemd.conf
-rw-r--r-- 1 root root 449 1 jun 02.28 tmp.conf
-rw-r--r-- 1 root root 622 1 jun 02.28 x11.conf
And the only thing possibly close is; d /run/user 0755 root root 10d
from systemd.conf.
Last edited by swanson (2012-06-08 07:20:28)

Nope, error still there and no clue what's happening. It occurs without me trying to mount anything, no usb's, no phones and no disks.

Run 'echo' command at boot.

Hey!
I am trying to run the following command at boot:
"echo 10 > /sys/class/backlight/acpi_video0/brightness"
So far I've tried in /etc/rc.local. That didn't work
Any thoughts?

I can think of a primitive way to do it, but there's probably a better (and simpler) way than this...
Edit ~/.xinitrc and add your command above the "exec ..." line:
$ nano ~/.xinitrc
echo 10 > /sys/class/backlight/acpi_video0/brightness &
exec ck-launch-session gnome-session
The "&" at the end should be probably added in, for good measure. Backgrounding this task is (probably) a good idea, else your GNOME session (or whatever DE/WM you use) may not start.
Then edit your sudoers file, so that it doesn't ask for a password:
$ sudo EDITOR=nano visudo
Defaults editor=/usr/bin/nano
root ALL=(ALL) ALL
dspider ALL=(ALL) ALL
dspider ALL=NOPASSWD: /bin/mount, /bin/umount
dspider arch=NOPASSWD: /sbin/reboot, /sbin/poweroff, /usr/bin/pacman -Syu, /bin/echo 10 > /sys/class/backlight/acpi_video0/brightness
The easier way is to use the "-b" flag from gtk-redshift (inspired by f.lux):
# pacman -S redshift
$ gtk-redshift -l 44.42:26.10 -b 0.5 -g 0.8 -t 6500:3800 -m vidmode &
Last edited by DSpider (2012-09-26 07:16:29)

[SOLVED] Silent Boot - Systemd not shutting up

I have followed all the instructions over here: https://wiki.archlinux.org/index.php/Silent_boot
I have done everything. But Systemd still won't fully shut up. There is a line on every boot: "Starting version 218" (I believe it is stating systemd's version)
I don't think I get this message on my previous arch installation about 2 years ago.
The Arch installation is fresh and fully updated.
I am using rEFInd as my boot loader. Here is the menu entry that I use
menuentry "Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume Boot
loader /vmlinuz-linux
initrd /initramfs-linux.img
graphics on
options "root=UUID=4b3977bd-a39f-46ab-980f-648c695a0554 rootfstype=ext4 rw add_efi_memmap quiet loglevel=3 vga=current rcutree.rcu_idle_gp_delay=1 "
Anybody know how to get rid of this?
At the very least anybody know who is spewing this line? systemd? rEFInd?
Thanks.
Last edited by efronberlian (2015-01-11 18:16:10)

jakschu wrote:add rd.udev.log-priority=3 to your kernel command line.
https://bbs.archlinux.org/viewtopic.php … 1#p1488281

Command setenv boot-file ""

The command is putting "" in the field instead of making it blank. Any ideas?

yep,
not sure why its doing that but if you want to set boot-file blank as per default, do:
<ok> set-default boot-file <cr>
note: not set-defaults<------
hope this helps

Command on boot - systemd tmpfile

Similar Messages

Maybe you are looking for