OG Locate is nice, and it would have found hwclock indeed, but
OG the database should be up-to-date. Many home users don't run it.
OG I didn't know if James did, and thus did not mention it.
AFAIR, updatedb is run once on install... And updatedb is installed in
cron by default on RH. So most
"Stanislav Malyshev a.k.a Frodo" wrote:
PLP find $MANPATH -name "clock*" -print
Uh-oh... locate is perfectly good command, why not to use it? Like in
"locate clock.8", which would explain everything.
--'
Again, a good strategy, except on RH 5.0-5.2 there is no clock.8 file.
There is a
On Fri, 19 Mar 1999, James Olin Oden wrote:
"Stanislav Malyshev a.k.a Frodo" wrote:
PLP find $MANPATH -name "clock*" -print
Uh-oh... locate is perfectly good command, why not to use it? Like in
"locate clock.8", which would explain everything.
--'
Again, a good strategy, except on RH
OG man 8 clock
man 8 hwclock
Also, man 8 setclock
At least on my RH. It was "clock" somewhere in time, but it moved to be
hwclock - I think to emphasize that it sets hardware clock, not just some
volatile "system time" :)
OG Well, the man page for clock(8) may be missing on your system, but
OG
James Olin Oden [EMAIL PROTECTED] writes:
Well, the man page for clock(8) may be missing on your system, but
who's to blame if that is the case?
I suppose Red Hat would be to blame as it is one of their distributions (RH 5.0
and 5.2). I will search the net for this man page.
Or maybe
"Stanislav Malyshev a.k.a Frodo" wrote:
OG man 8 clock
man 8 hwclock
Also, man 8 setclock
At least on my RH. It was "clock" somewhere in time, but it moved to be
hwclock - I think to emphasize that it sets hardware clock, not just some
volatile "system time" :)
That did it. I am using
