On May 10, 2012, at 3:40 PM, Mike La Spina wrote: >> The closest google turns up is here: >> http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html >> I did run `svccfg -s boot-archive setprop start/timeout_seconds=180` but >> the /var/svc/log/system-boot-archive:default.log seems to indicate that >> I'm only getting 60 seconds: >> >> [ May 10 12:54:03 Enabled. ] >> [ May 10 12:54:06 Executing start method >> ("/lib/svc/method/boot-archive"). ] [ May 10 12:55:06 Method or service >> exit timed out. Killing contract 19. ] >> >> # svccfg -s boot-archive listprop | grep timeout >> >> start/timeout_seconds count 180 >> stop/timeout_seconds count 3 > > The only thing I can think of is ... did you refresh the active service > manifest? > > e.g. > > svcadm refresh boot-archive:default
This seems to have done the trick, thanks! But, shouldn't running svccfg's setprop have stuck without running "refresh"? Cheers, Ian _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
