Hi Steve,
sorry, I did not notice that you pass -L to statd.
I now removed the -L option from statd as well and it still is running after boot.
After reverting back to original state (exec sm-notify in pre-start and statd -L) the log says:
init: statd pre-start process (714) terminated with status 1
@Dave: How did you tweak sm-notify to get more debug? I added -d to its start but did not get any messages about "Cannot create ..." or something.
After changing "start on" to start on (started portmap and local-filesystems)
it is working here as well but I do not have /var on a separate FS on that machine but / maybe still is mounted ro before local-filesystems?
But why do you start sm-notify manually and then use statd -L instead of just starting statd without -L ?
Hi Steve,
sorry, I did not notice that you pass -L to statd.
I now removed the -L option from statd as well and it still is running after boot.
After reverting back to original state (exec sm-notify in pre-start and statd -L) the log says:
init: statd pre-start process (714) terminated with status 1
@Dave: How did you tweak sm-notify to get more debug? I added -d to its start but did not get any messages about "Cannot create ..." or something.
After changing "start on" to
start on (started portmap and local-filesystems)
it is working here as well but I do not have /var on a separate FS on that machine but / maybe still is mounted ro before local-filesystems?
But why do you start sm-notify manually and then use statd -L instead of just starting statd without -L ?