It probably would have been sufficient to "svcadm restart ntp" without
adding the symlink. I suspect that the SMF property that controls the
start method got changed in the manifest during the upgrade.
Unfortunately, the manifest change does not get reflected in the repository
until the manifest-import service runs. Restarting ntp will get it to see
the new property value and you shouldn't have any problems on subsequent
reboots.
Could you invoke "svcprop -p start/exec ntp" and see what you get as
output?
tom
Gary Mills writes:
> I just upgraded from OS 0906 to snv_127.
> I got this error on the boot of snv_127:
>
> svc.startd[7]: [ID 652011 daemon.warning] svc:/network/ntp:default: Method
> "/lib/svc/method/xntp" failed with exit status 127.
> svc.startd[7]: [ID 748625 daemon.error] network/ntp:default failed:
> transitioned to maintenance (see 'svcs -xv' for details)
>
> The log file showed this:
>
> [ Nov 14 11:02:10 Executing start method ("/lib/svc/method/xntp"). ]
> /sbin/sh[1]: exec: /lib/svc/method/xntp: not found
> [ Nov 14 11:02:10 Method "start" exited with status 127. ]
>
> The problem was that the method script was now:
>
> /lib/svc/method/ntp
>
> This is the workaround:
>
> # cd /lib/svc/method
> # ln -s ntp xntp
>
> I couldn't find a bug report for this problem.
> --
> This message posted from opensolaris.org
> _______________________________________________
> indiana-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
