On Tue, Jan 20, 2015 at 05:04:26PM -0500, Ted Unangst wrote: > Since we're poking at shutdown, I think it should parse years with a > century so that conscientious sysadmins can specify unambiguous dates. > > Note that specifying dates past 2038 doesn't work (with or without this > diff) because the sleep code is not y2k38 safe. > > Index: shutdown.8 > =================================================================== > RCS file: /cvs/src/sbin/shutdown/shutdown.8,v > retrieving revision 1.39 > diff -u -p -r1.39 shutdown.8 > --- shutdown.8 19 Nov 2007 08:51:49 -0000 1.39 > +++ shutdown.8 20 Jan 2015 21:55:52 -0000 > @@ -122,7 +122,7 @@ may be the word > specify a future time in one of two formats: > .Ar +number , > or > -.Ar yymmddhhmm , > +.Ar ccyymmddhhmm , > where the year, month, and day may be defaulted > to the current system values. > The first form brings the system down in
the date formats in utils like date(1) use the format ccyymmddHHMMSS. in the past we moved the docs to consistently use that format. not sure why we didn;t touch shutdown but it might be better to use that notation here too. it would be more consistent, and it works along with the fact that the year/month/day values can be left out, whereas you have to give hours and minutes (if i understand correctly). jmc
