02-19-2013
The clock is correct, the timezone setting is not for some reason. Please provide more clues/evidences.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
There is a requirement to create a file everyday using the cronjob with the date as its name.
any suggestions for the crontab command that'll serve this purpose?
e.g.
02 30 * * * touch abcd.`date +%d.%m.%y`
needless to say.. this doesn't work..
looking fwd to lots of... (7 Replies)
Discussion started by: pranavagarwal
7 Replies
2. Shell Programming and Scripting
Hi,
We have a server in US and hence while the command "date" is given it gives the output in EDT. If I want the date output in MET, how can I get it. Please let me know how I could do it in the script which is ksh. Thanks. (1 Reply)
Discussion started by: jmathew99
1 Replies
3. Solaris
Hello,
I was under the impression that the Header of the prtdiag output shows the hardware vendor information in the section between System Configuration and sun4u/sun4us. But on some Solaris machines which are running on Fujitsu hardware, the vendor is shown as Sun Microsystems in this... (8 Replies)
Discussion started by: chattygk
8 Replies
4. Solaris
Hello Guru's
I'm trying to take the output of solaris top command and output to a txt file every few minutes. The issue that I'm experiencing is that I can run the following:
#!/bin/bash
#
logfile="/usr/mvf/morris/top.log"
# echo... (2 Replies)
Discussion started by: littlemorris
2 Replies
5. Solaris
While getting the total disk space in solaris machine using df -k command, i am getting the same disk info for every user available in that system.
Is there any way to remove it.
Filesystem 1024-blocks Used Available Capacity Mounted on
rpool/ROOT/solaris 573898752... (3 Replies)
Discussion started by: prasankn
3 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I created some cron entries in one of the 4 zones in Solaris 10. Now I want to edit it and unable to find the crontab file
crontab -l gives : unable to open crontab file
/usr/spool/cron/crontabs doesn't have the crontab file
Hence, I did ifconfig -a and tried to login with the 3... (2 Replies)
Discussion started by: Rossdba
2 Replies
7. Solaris
Hi,
First post.
I have a script that I am having a little trouble with and I hope someone can help.
I will post the code for your input, but I want to read the lines of a file and use this as input to a command in a while loop...
#!/bin/sh
#
#
### Variables
MSG=/tmp/tmptest.txt... (7 Replies)
Discussion started by: dakelly
7 Replies
8. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
LEARN ABOUT NETBSD
inittodr
INITTODR(9) BSD Kernel Developer's Manual INITTODR(9)
NAME
inittodr -- initialize system time
SYNOPSIS
void
inittodr(time_t base);
DESCRIPTION
The inittodr() function determines the time and sets the system clock. It tries to pick the correct time using a set of heuristics that
examine the system's battery-backed clock and the time reported by the file system, as given in base. Those heuristics include:
o If the battery-backed clock has a valid time, and is not significantly behind the time provided by base, it is used.
o If the battery-backed clock does not have a valid time, or is significantly behind the time provided in base, and the time provided in
base is within reason, base is used as the current time.
o If the battery-backed clock appears invalid, and base appears non-sensical or was not provided (was given as zero), an arbitrary base
(typically some time within the same year that the kernel was last updated) will be used.
Once a system time has been determined, it is stored in the time variable.
DIAGNOSTICS
The inittodr() function prints diagnostic messages if it has trouble figuring out the system time. Conditions that can cause diagnostic mes-
sages to be printed include:
o There is no battery-backed clock present on the system.
o The battery-backed clock's time appears nonsensical.
o The base time appears nonsensical.
o The base time and the battery-backed clock's time differ by a large amount.
SEE ALSO
clock_ymdhms_to_secs(9), resettodr(9), time_second(9)
BUGS
Some systems use heuristics for picking the correct time that are slightly different.
BSD
September 6, 2006 BSD