Sponsored Content
Full Discussion: Wrong Time on Server
Top Forums UNIX for Dummies Questions & Answers Wrong Time on Server Post 302543568 by fpmurphy on Monday 1st of August 2011 09:13:42 AM
Old 08-01-2011
This option may not be available to you but one way would be to shut the system down for 10 minutes or whatever the time delta is and bring it back up with the correct time set.
 

9 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

DCHP server assigning a wrong Address

Pls could you help me diagnose my problem. I have a system which is a DHCP server and also the Remote Access Server. The DHCP server allocate normal address within the scope range to the LAN system. why it allocates abitrary number such as 169.254.217.90 255.255.0.0 class B address to the remote... (1 Reply)
Discussion started by: kayode
1 Replies

2. Programming

setitimer expires in wrong time

I set a timer using setitimer to expire every 30 ms. Usually it does. But sometimes it takes ~ 700 ms between 2 successive arousals (expirations). The timing is crucial for me. The process with the timer is almost the only one running on the computer. How do I overcome this problem? (1 Reply)
Discussion started by: inna
1 Replies

3. UNIX for Advanced & Expert Users

How To Provide Time Sync Using Nts-150 Time Server On Unix Network?

can anybody tel lme,how to instal NTS -150 on a unix network,it needs some patch to fetch time frm serve,,?? (2 Replies)
Discussion started by: pesty
2 Replies

4. AIX

Time Zone for a User Different From Server Time

Hi, A server runs on EDT. Can I set a user with time-zone GMT without changing the server time? regards, Roshni (1 Reply)
Discussion started by: RoshniMehta
1 Replies

5. UNIX for Dummies Questions & Answers

Made something wrong in server

hello friends, l was using this command to empty tmp directory but l made this by mistake : and l cant reach my sites now. what l did ??? ---------- Post updated 11-13-11 at 12:07 AM ---------- Previous update was 11-12-11 at... (3 Replies)
Discussion started by: rcpkrc
3 Replies

6. Solaris

modifying date and time and time zone on solaris 5.10 with (redundant server) veritas

I have a cluster of two Solaris server (veritas cluster). one working and the other is standby I am going to change the date on them , and am looking for a secure solution as it is giving an important service. my opinion is that the active one doesn't need to be restarted (if I don't change the... (1 Reply)
Discussion started by: barry1946
1 Replies

7. UNIX for Dummies Questions & Answers

Cron job executed at wrong time

Dear *nix users. I'm on Mac OS 10.6 / Terminal and try to use crontab to schedule two scripts every 30 minutes and every 41 minutes. I followed the man instructions and created / installed a crontab file for the current user:crontab -e with the following content */30 * * * *... (4 Replies)
Discussion started by: moxnos
4 Replies

8. Solaris

Wrong time zone for non root user

I have a Solaris-11 zone, which is newely build. Since I am in PST time zone, so I set it with this command. It shows me date correctly with correct time zone, but when I switch it to a non root user and run below java command, it is not showing correct time zone. Not sure, how to set it.... (2 Replies)
Discussion started by: solaris_1977
2 Replies

9. UNIX for Dummies Questions & Answers

VxWorks RTC time giving wrong value at random times

I am seeing a scenario where in if the TIMEZONE environment variable value is set to nothing i.e. putenv "TIMEZONE=" the hardware clock is +1 to software clock.Pasted below the results displayed: -> envShow (global environment) 0: TSC_TIME_FROM_RESET=420150.971529 seconds 1:... (0 Replies)
Discussion started by: snehavb
0 Replies
SHUTDOWN(8)						      System Manager's Manual						       SHUTDOWN(8)

NAME
shutdown - close down the system at a given time SYNOPSIS
shutdown [ -k ] [ -r ] [ -h ] [ -f ] [ -n ] time [ warning-message ... ] DESCRIPTION
Shutdown provides an automated shutdown procedure which a super-user can use to notify users nicely when the system is shutting down, sav- ing them from system administrators, hackers, and gurus, who would otherwise not bother with niceties. Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a future time in one of two formats: +number and hour:min. The first form brings the system down in number minutes and the second brings the system down at the time of day indicated (as a 24-hour clock). At intervals which get closer together as apocalypse approaches, warning messages are displayed at the terminals of all users on the sys- tem. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are disabled by creating /etc/nologin and writing a message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed just before shutdown exits. At shutdown time a message is written in the system log, containing the time of shutdown, who ran shutdown and the reason. Then a termi- nate signal is sent to init to bring the system down to single-user state. Alternatively, if -r, -h, or -k was used, then shutdown will exec reboot(8), halt(8), or avoid shutting the system down (respectively). (If it isn't obvious, -k is to make people think the system is going down!) With the -f option, shutdown arranges, in the manner of fastboot(8), that when the system is rebooted the file systems will not be checked. The -n option prevents the normal sync(2) before stopping. The time of the shutdown and the warning message are placed in /etc/nologin and should be used to inform the users about when the system will be back up and why it is going down (or anything else). FILES
/etc/nologin tells login not to let anyone log in SEE ALSO
login(1), reboot(8), fastboot(8) BUGS
Only allows you to kill the system between now and 23:59 if you use the absolute time for shutdown. 4th Berkeley Distribution November 16, 1996 SHUTDOWN(8)
All times are GMT -4. The time now is 08:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy