FS#47241 - [systemd] 228 makes X server fail to start with custom /tmp mount options
Attached to Project:
Arch Linux
Opened by trendkiller (trendkiller) - Wednesday, 02 December 2015, 22:06 GMT
Last edited by Dave Reisner (falconindy) - Friday, 04 December 2015, 19:07 GMT
Opened by trendkiller (trendkiller) - Wednesday, 02 December 2015, 22:06 GMT
Last edited by Dave Reisner (falconindy) - Friday, 04 December 2015, 19:07 GMT
|
Details
Description:
After i upgraded systemd from 227 to 228, when i use custom mount options for /tmp, the X server fails to start on boot with the following message: Fatal server error: (EE) Could not create lock file in /tmp/.tx0-lock Then goes into a loop trying to start and failing. My fstab entry: tmpfs /tmp tmpfs rw,nodev,nosuid,mode=1700 These options worked fine with systemd 227. After i comment out the fstab entry it works with 228 too. |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 04 December 2015, 19:07 GMT
Reason for closing: Not a bug
Additional comments about closing: mode=1700 does what it says on the tin.
Friday, 04 December 2015, 19:07 GMT
Reason for closing: Not a bug
Additional comments about closing: mode=1700 does what it says on the tin.
why is mode=1700 a bad idea? it worked fine until systemd 228 upgrade
I asked for the difference in effective mount options because it seems to me like 228 has the *correct* behavior in actually honoring your mount options.