:) Very likely I snagged it from you. I recall a few months back discussing scripts to log the leap change and everybody was throwing down their scripts. :)
On Mon, Jun 25, 2012 at 8:55 AM, Fabian Wenk <[email protected]> wrote: > Hello > > On 25.06.2012 13:52, AlbyVA wrote: > >> Here is my shell script to watch the leap second change: >> >> #!/bin/sh >> for i in `seq 0 240` ; do ntptime | awk '/time d3/ {print $3" "$4" "$5" >> "$6" "$7}' | sed 's/,$//' ; sleep 0.5 ; done >> > > This looks very familiar :) > > I also have a script which will report the unix time on the same systems > during the leap second. I am curios how this will look like, but probably > the system time is only corrected over a longer time period, without any > additional second (as this would change the relationship between the > seconds since epoch and the human readable representation of date / time). > > report-timechange-unix.sh: > > ---8<-------------------------**----------------------- > #!/bin/bash > > echo "Log of unix time during 2 minutes:" > echo > for i in `seq 0 240`; do > date ; sleep 0.5 > done > > exit 0 > ---8<-------------------------**----------------------- > > To use this scripts, create a cron job at 30-Jun-2012 23:59 UTC. Adjust if > your system does not run on UTC, for example for the next leap second in > Western Europe (currently CEST) use something like this in cron (on one > line): > > 59 01 01 07 * /path/to/report-timechange-**unix.sh 2>&1 | /bin/mail > -s "unix time change log leap second (`hostname -s`)" [email protected] > > I recommend to test it trough cron with a time in just a few minutes in > the future. > > > > bye > Fabian > ______________________________**_________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/**pool <http://lists.ntp.org/listinfo/pool> >
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
