Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'See a possible Y2K bug in shutdown' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
See a possible Y2K bug in shutdown
Authored by: Cerberus on Sep 02, '03 10:33:55PM
Please read the man page again. It says:
may be the word 'now' (indicating an immediate shutdown) or specify a future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system values.
a little slower now... specify a future time... The orig post was on 9/2 but the command attempted to set a reboot for 8/31. I would therefore see this as a display bug in dealing with a date which is already in the past... As Rob stated, it might be fixed in 10.3 but then I would like to get clarification: What is 'fixed/different about this in 10.3? Does it change the command line to be in the future? Does it ignore it and not process the command?

Inquiring minds (and comprehending ones) want to know!

[ Reply to This | # ]

See a possible Y2K bug in shutdown
Authored by: ctparker333 on Sep 03, '03 01:14:14AM

The problem is that, using 10.2, if you try to use the shutdown command to shut down computer in the future, and you use the full time code (10 digits), the first 2 digits are read as the year. However if you set the first two digits as 03, the output has the year as 1903, not 2003. The trick is to only use 8 digits, then the computer uses to the current year.

I haven't played with 10.3 yet so I don't know what is different.



[ Reply to This | # ]
See a possible Y2K bug in shutdown
Authored by: aranor on Sep 03, '03 01:17:21AM

That's not the issue. I would bet that the original poster tried it as a future date, but the date became in the past by the time this was actually posted.



[ Reply to This | # ]