FS#36411 - systemd fails to start services on boot when /var is a symlink.

Attached to Project: Arch Linux
Opened by Kristóf Szalay (kzszalay) - Sunday, 04 August 2013, 13:17 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 05 August 2013, 00:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

systemd fails to start services on boot when /var is a symlink.

Probably a duplicate of  FS#31301 , I would like to add another use case for why would this be important: I am using an SSD+HDD combo, and have symlinked my /var to the HDD to prolong the SSD lifespan.
Symlinking instead of creating a whole new partition is better, because I wouldn't need to resize the partition when it is full.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 05 August 2013, 00:30 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Sunday, 04 August 2013, 13:38 GMT
Use a bind mount. You configuration will cause issues with pacman-4.2.
Comment by Kristóf Szalay (kzszalay) - Sunday, 04 August 2013, 23:39 GMT
You are right, I was not aware I could bind mount a subtree instead of the whole FS.

Loading...