> [moving to -hackers]
[I'm going to loose the rest of this thread since I am not on hackers :-(]
>
> "Rodney W. Grimes" <[EMAIL PROTECTED]> writes:
> > So when can we see this commited....
>
> Already done (-CURRENT only). I've had requests (notably from Yan
> Koum) to backport it to -STABLE, but I won't do it so close to a
> release.
I've already done the ``backport'', but your correct in that it is
a wee bit close to release, actually too late as we are in code freeze
and this is a new feature :-).
>
> > the only thing I would like
> > changed is actually a general format of output change in /etc/rc.network,
> > if you have a few of the ``tcp_*'' knobs set the line length gets
> > a bit long, could be change the ``echo -n'''s to ``echo \t'' and loose
> > the trailing ``echo '.'''.
>
> I don't consider that much of a problem, except in cases where
> individual scripts / options produce output which breaks the line
> (this is mostly a problem with ports). I wouldn't mind the changes you
> suggest, but I don't care enough to actually go ahead and do it.
>
> One thing I'd like very much, though, would be to have the output of
> fsck -p logged somehow - but since we don't have anything mounted rw
> when fsck runs, it's a bit hard to log to disk. You could of course
> do something like this:
Actually I would like _all_ the output from /etc/rc* to be avaliable
after boot. It should be in the syscons scroll back buffer, we just
need a little program to go grab it and stuff it away at the end of
/etc/rc runs. This would be a big win for remote admining and trying
to figure out what went wrong during the last boot without having to
drive down and hook up a console of some form. I know we could hang
serial consoles on all of them, but why spend money on hardware when
the problem can be solved with software :-).
>
> fsck_output="$(/sbin/fsck -p)"
> /sbin/mount -at nonfs
> echo "${fsck_output}" >/var/run/fsck.boot
>
> but then you wouldn't be able to see the output while it runs. The
> only solution I can think of is the following:
>
> fsck_output="$(/sbin/fsck -p | /bin/tee /dev/console)"
> /sbin/mount -at nonfs
> echo "${fsck_output}" >/var/run/fsck.boot
>
> but I don't expect people to be happy about moving tee(1) from
> /usr/bin to /bin.
And solving only 1 piece of output from /etc/rc is an incomplete
concept. I really like to know if ntpdate stepped my clock 230000 seconds
for some reason, thats why this (usually means a clock chip has gone
zonkers :-)):
Index: rc.network
===================================================================
RCS file: /home/ncvs/src/etc/rc.network,v
retrieving revision 1.39.2.11
diff -u -r1.39.2.11 rc.network
--- rc.network 1999/09/03 08:57:26 1.39.2.11
+++ rc.network 1999/09/12 19:02:01
@@ -257,7 +257,7 @@
fi
if [ "X${ntpdate_enable}" = X"YES" ]; then
- echo -n ' ntpdate'; ${ntpdate_program} ${ntpdate_flags} >/dev/null 2>&1
+ echo -n ' ntpdate'; ${ntpdate_program} ${ntpdate_flags} >>/var/log/ntpdate
+2>&1
fi
if [ "X${xntpd_enable}" = X"YES" ]; then
And a whole slew of others... they just has to be a better way!!
--
Rod Grimes - KD7CAX - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
