On Mon, Jan 13, 2014 at 04:38:45PM -0000, Jarod wrote:
> The /var/log/upstart/statd-mounting*.log for the 2 other filesystems also
> contained "Terminated" as their only line.
That much is expected.
> I think that all of those errors are a result of /var not being mounted
> when the process is started. /var resides on a separate LV as do /boot,
> /home, /usr, /var and /tmp.
Oh, thanks, that's helpful to know. It's possible that we've overlooked a
dependency that rpc.statd has on /var being mounted... I had believed that
rpc.statd didn't need /var given that it's located in /sbin, but strings
/sbin/rpc.statd does show a few references to /var/. I'll see what I
can find out here.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Mon, Jan 13, 2014 at 04:38:45PM -0000, Jarod wrote: upstart/ statd-mounting* .log for the 2 other filesystems also
> The /var/log/
> contained "Terminated" as their only line.
That much is expected.
> I think that all of those errors are a result of /var not being mounted
> when the process is started. /var resides on a separate LV as do /boot,
> /home, /usr, /var and /tmp.
Oh, thanks, that's helpful to know. It's possible that we've overlooked a
dependency that rpc.statd has on /var being mounted... I had believed that
rpc.statd didn't need /var given that it's located in /sbin, but strings
/sbin/rpc.statd does show a few references to /var/. I'll see what I
can find out here.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>