search for: yyyymmddhhmmss

...nsure => absent". I ended up fixing most things with puppet and a few by hand, but it would be nice to have a feature that allows for a roll back (of some sort). Has any work been done in that area? Maybe the puppetmaster tags something in: /var/lib/puppet/state/tag/current -> YYYYMMDDHHMMSS.newer which is created when configurations are compiled for a particular client /var/lib/puppet/state/tag/previous -> YYYYMMDDHHMMSS.older Which is the previous configuration. Then we could say something like: puppetrb --tag <tag>@YYYYMMDDHHMMSS.older Once that run is done, cur...

These are date and times in the format YYYYMMDDhhmmss. I would like to take this column and make a chron object form them. I have tried a couple of the split family of functions but they need character input here is the data: date.time <- c(19851001001500, 19851001003000, 19851001004500, 19851001010000, 19851001011500, 19851001013000, 198510010...

...d didn't find much. Is anyone using the Monitor application? I have it working but there is a really big drawback. The files are always called the same thing, which means if I make 2 calls one after the other the first recording is lost. I half expected Monitor to use something like ZAP-2-1-<yyyymmddhhmmss>-in/out.wav for it's filenames but it just uses the channel eg Zap-2-1-in.wav Zap-2-1-out.wav has anyone found a solution to this? Thanks Andy

...-------- Problems with ssh-keygen.1: Invalid Sx reference - not a section on this page. --- ssh-keygen.1-unpatched 2013-05-25 15:24:47.868323922 -0400 +++ ssh-keygen.1 2013-05-25 15:24:47.508323929 -0400 @@ -466,7 +466,7 @@ The start time may be specified as a date in YYYYMMDD format, a time in YYYYMMDDHHMMSS format or a relative time (to the current time) consisting of a minus sign followed by a relative time in the format described in the -.Sx TIME FORMATS +.Em TIME FORMATS section of .Xr sshd_config 5 . The end time may be specified as a YYYYMMDD date, a YYYYMMDDHHMMSS time or

Hi all, I found that the figure returned by MSet::get_matches_estimated() varies depending on how results are to be sorted. For instance, in my index, value 4 contains date and time in the format "yyyymmddhhmmss". For the same query, the number of results will be estimated to 20000+ when results are first sorted by date and time with set_sort_by_value_then_relevance(4) and to only 100 if I use set_sort_by_relevance(). The first figure is the correct one. Note that the MSet is obtained with Enquire::g...

I would have never imagined that I''d be bitten by the Y2038 bug someday... but it just happened and, trust me, it hurts! I have to deal with a database containing datetime fields with dates up to 2050 and more. ActiveRecord raises an exception because Ruby''s Time class implementation. Besides running Ruby on a 64-bit platform, what can be done to avoid that? Does a