"Paul Kraus" writes: > On 9/24/07, Michael Schuster <[EMAIL PROTECTED]> wrote: > > > I recently started seeing zfs chattiness at boot time: "reading zfs config" > > and something like "mounting zfs filesystems (n/n)". > > > > Is this really necessary? I thought with SMF the times where every script > > announced its' existance had gone (and good thing, too). > > > > Can't we print something only if it goes wrong?
It would be sad to return to a world where useful messages about things going wrong were overwhelmed by subsystems simply announcing their existance to the world. I've been on the fence about whether this case crosses that threshold. > Unfortunately, sometimes something goes wrong and nothing > realizes. I have always advocated being able the tune the chattiness > of booting. If I had a system (under Solaris <10) that was hanging on > boot (or more frequently on shutdown) I would add a bunch of echos to > the scripts /sbin/rc0, /sbin/rc2, etc. Then I could clearly see what > was hanging. > > I would love SMF to support a boot (and shutdown) option to > tell me what services it is trying to start/stop/restart to the > console so I can find the one that misbehaves (and doesn't know it). boot -m verbose does this for startup. (Note that both error messaging and startup messaging were improved significantly in u3/u4/NV. There were some bugs before that which made the experience less friendly.) Bug 6195169 asserts it should work for shutdown too. (Which I agree with.) There are also some other "chatty" modes that I think would be useful, but I'll leave that for a conversation on smf-discuss. liane _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
