On Thursday 13 Dec 2012 10:51:02 you wrote:
> That's a very good point; probably all of these sockets will end up in /run
> rather than /var (as they once did). Maybe the issues I'm seeing after boot
> are not related to sockets being masked as I assumed. I have no idea what
> else it could be, t
On Wednesday 12 Dec 2012 17:53:23 Tom Gundersen wrote:
> On Wed, Dec 12, 2012 at 4:02 PM, Paul Gideon Dann
wrote:
> Is syslog.socket giving you problems? Could you paste the unit file?
> On my system the socket is located at /run/systemd/journal/syslog, so
> After=-.mount is correct.
That's a ve
On Wed, Dec 12, 2012 at 4:02 PM, Paul Gideon Dann wrote:
> Thanks for your suggestions. I added /var to fstab and rebooted, but it was
> ordered lower down that specifying "Before=sockets.target":
So no socket is After=var.mount. The question is: which one should be?
On my system there should be
On Wednesday 12 Dec 2012 15:03:47 you wrote:
> I wasn't aware of the bootup manpage. That's incredibly helpful; thank you.
> I'll try ordering before a few more of those targets and see if I get
> anywhere. However, based on the bootchart, none of the targets appear
> before the first socket unit
On Wednesday 12 Dec 2012 08:05:26 Dave Reisner wrote:
> > That's what I hoped too. I've tried several approaches. I'm trying a
> > mount unit here, because I was hoping there might be a bit more magic to
> > it. However, it does mean that I had to hardcode the mount path (%H
> > doesn't seem to w
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
On Wed, Dec 12, 2012 at 12:10 PM, Paul Gideon Dann wrote:
> I'm trying a mount
> unit here, because I was hoping there might be a bit more magic to it.
Yes, it is.
> However, it does mean that I had to hardcode the mount path (%H doesn't seem
> to work)
At the moment %H and friends only work on
On Wed, Dec 12, 2012 at 11:10:24AM +, Paul Gideon Dann wrote:
> On Wednesday 12 Dec 2012 00:40:43 Tom Gundersen wrote:
> > Sockets in /var should automatically be ordered After=var.mount, so
> > this should in theory just work. How are you mounting /var? I assume
> > an fstab entry would not do
On Wednesday 12 Dec 2012 00:40:43 Tom Gundersen wrote:
> Sockets in /var should automatically be ordered After=var.mount, so
> this should in theory just work. How are you mounting /var? I assume
> an fstab entry would not do in your setting, so I guess you somehow
> generate a custom var.mount fil
On Tue, Dec 11, 2012 at 4:36 PM, Paul Gideon Dann wrote:
> I'm migrating a diskless cluster from initscripts to systemd. The problem I
> have is that the nodes each need to mount their own separate /var (identified
> by hostname) from the NFS server when they boot.
I have never done something li
Hello all,
I'm migrating a diskless cluster from initscripts to systemd. The problem I
have is that the nodes each need to mount their own separate /var (identified
by hostname) from the NFS server when they boot.
With initscripts, I used a sysinit_end hook to do the job, which worked pretty
11 matches
Mail list logo
