"init: statd pre-start process (712) terminated with status 1"
Thats the only line about it in boot.log with --verbose
service portmap is running after boot, so I tried to comment out the "exec sm-notify" line.
After that statd service is runng after reboot.
So why is sm-notify failing here? Is it really required to exec it in this place?
AFAIK sm-notify will be run by statd automatically when it starts up, so IMO the "exec sm-notify" is superfluous anyway.
The sm-notify man page says:
"When rpc.statd is started it will typically started sm-notify but this is configurable. "
and from statd man page:
-L, --no-notify Prevents rpc.statd from running the sm-notify command when it starts up, preserving the existing NSM state number and monitor list.
Note: the sm-notify command contains a check to ensure it runs only once after each system reboot. This prevents spurious reboot notification if rpc.statd restarts without the -L option.
Hi Steve,
its failing in pre-start:
"init: statd pre-start process (712) terminated with status 1"
Thats the only line about it in boot.log with --verbose
service portmap is running after boot, so I tried to comment out the "exec sm-notify" line.
After that statd service is runng after reboot.
So why is sm-notify failing here? Is it really required to exec it in this place?
AFAIK sm-notify will be run by statd automatically when it starts up, so IMO the "exec sm-notify" is superfluous anyway.
The sm-notify man page says:
"When rpc.statd is started it will typically started sm-notify but this is configurable. "
and from statd man page:
-L, --no-notify
Prevents rpc.statd from running the sm-notify command when it starts up, preserving the existing NSM state number and monitor list.
Note: the sm-notify command contains a check to ensure it runs only once after each system reboot. This prevents spurious reboot notification if
rpc.statd restarts without the -L option.
-Marc