Allegedly, on or about 05 May 2017, François Patte sent: > var.mount: Directory /var to mount over is not empty > > Why does cups creates directories in /var before /var is mounted? Sounds like yet another systemd snafu. Previously system start-up scripts were run sequentially. And if something required something else to be available first, then you arranged the order of scripts accordingly. Now everything tries to start concurrently, and some things don't always start up with the same speed each boot, so your sequencing can change (what worked last week, might not today). A similar remedy exists, now, where scripts can wait for particular things to happen before they do their bit (such as having cups wait for the network to be up and for var to be mounted), but not all those conditions have been anticipated, so various scripts work more by luck than good planning. There is another approach: If you don't need var to be a separate mount, and most people don't, var can simply be a directory in root. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. Linux servers are always being dæmonised... _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
