On Wednesday 12 Dec 2012 14:17:34 Tom Gundersen wrote: > I'm not able to reproduce this problem. I don't see the need for > sockets-pre.target. It should be possible to simply specify your mount > in /etc/fstab (obviously this only works in this test case, as the > hostname will be hardcoded), and all sockets should get ordered > correctly. > > Could you try that (remember doing "systemctl daemon-reload" after > editing fstab) and then doing "systemctl show <problematic>.socket | > grep After" to see if it worked? If it did not, please post the socket > unit in question. Thanks for your suggestions. I added /var to fstab and rebooted, but it was ordered lower down that specifying "Before=sockets.target": http://giddie.homeip.net/screenshots/cluster-node-var-mount-boot-chart- fstab.png # systemctl show syslog.socket | grep After After=-.mount Paul
