> One thing that can happen "three minutes later" is
> is the execution of
> sysidtool, after doing some discovery. If this is
> is the case, then the
> times on the system/sysidtool instances will
> ll overlap with the ones
> above.
If that is what is happening, how do I work around it/fix it?
Adding logs.
/Henrik
bash-3.00# cat /var/svc/log/network-nis-client\:default.log
[ Jul 11 14:42:14 Disabled. ]
[ Jul 11 14:42:15 Rereading configuration. ]
[ Jul 11 14:44:38 Enabled. ]
[ Jul 11 14:48:05 Executing start method ("/lib/svc/method/yp") ]
[ Jul 11 14:48:05 Method "start" exited with status 0 ]
[ Jul 11 14:48:06 Stopping because service disabled. ]
[ Jul 11 14:48:06 Executing stop method (:kill) ]
bash-3.00# cat /var/svc/log/system-sysidtool\:
system-sysidtool:net.log system-sysidtool:system.log
bash-3.00# cat /var/svc/log/system-sysidtool\:system.log
[ Jul 11 14:44:22 Enabled. ]
[ Jul 11 14:44:24 Rereading configuration. ]
[ Jul 11 14:48:05 Executing start method ("/lib/svc/method/sysidtool-system") ]
[ Jul 11 14:48:29 Method "start" exited with status 0 ]
bash-3.00# cat /var/svc/log/system-sysidtool\:net.log
[ Jul 11 14:44:24 Enabled. ]
[ Jul 11 14:44:24 Rereading configuration. ]
[ Jul 11 14:44:44 Executing start method ("/lib/svc/method/sysidtool-net") ]
[ Jul 11 14:48:04 Method "start" exited with status 0 ]
bash-3.00#
This message posted from opensolaris.org
