l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Feb 16 18:03

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] time jumps 8 hours
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] time jumps 8 hours

On Fri, 15 Feb 2002, eric nelson wrote:
> Thanks.  I did find today that there is nothing in the cron.  I'll check 
> inetd.  Do you recommend setting the bios clock to local time?  I guess I 
> should use a high debug level of logging, so there's lots of data.  What 
> other files besides /var/log/messages?  
> I'll be away from work 3 days, might get back to you if I still can't figure 
> it out.  make files don't work too well with this situation :~(

Not all jobs will always show up in cron as by root or local users. I have
found /etc/cron.*/*

See if you have these, and review them too.

If after checking /var/spool/cron, /etc/cron*, /etc/at* and verifying that
you have no other at/cron packages (cron, anacron, etc) installed, and no
daemonized ntp clients, and reviewing log files to see when the
date/time-stamps change (the change in time should tell you *when* the
problem is occuring) and none of these helps you to find the offending
app, perhaps it is being called into being by another system update

This makes it more difficult. The time that the event occurs should help
you to narrow the group of apps that could call it. Disable half and see
if it goes away, if it does, then examine the half you disabled and
re-enable half. If it comes back, then suspect the 25% you have
left. Continue in this binary search and divide till you find it.

Also? Maybe do a man -k date and man -k clock and man -k time looking for
applications that can change the clock. Then mv these to different names
(like $0.oirg) and then write a bash wrapper that records PPID and
date/time into a file as well as a ps -auxw | grep $PPID to see the name
of the process and dump this info into a file, and then pass on the args
$@ to the real application $0.orig)

This seems time consuming, but is one of the many many approaches you
have available at your disaposal to solve this problem. Others here may
have other alternatives.

If you have found all clock/date modifying binaries on your system, and
wrapped them to still find nothing, suspect multiple personality disorder
or someone pulling a prank on you. (Hope my general joke is not

When you all were talking about Linux newbies:
 I still consider myself a *NIX newbie. ]:>


Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-----) C++$(++++) U++++$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++>++++ h(++)>+ r*>? z?
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!