OK, it makes some more sense now. The range of digits in the octal system is fromĀ 0 to 7, so it would complain with "08" and "09" (but not with "10" which would then be "8" in octal), but why would command line utilities assume you are encoding numeric values as octal? Now I notice many people have stumble on the same problem. There should be a straight forward way to encode from "HH:MM:SS" to seconds. I doubt that the date utility would assume you are computing numbers as octal.
- Is there a POSIX compliant way of turning a "HH:MM... lbrtchx
- Re: Is there a POSIX compliant way of turning a &q... Dan Purgert
- Re: Is there a POSIX compliant way of turning ... lbrtchx
- Re: Is there a POSIX compliant way of turning a &q... Alain D D Williams
- Re: Is there a POSIX compliant way of turning ... lbrtchx
- Re: Is there a POSIX compliant way of turn... Alain D D Williams
- Re: Is there a POSIX compliant way of ... lbrtchx
- Re: Is there a POSIX compliant wa... Alain D D Williams
- Re: Is there a POSIX complian... Greg Wooledge
- Re: Is there a POSIX compliant wa... David Wright
- Re: Is there a POSIX compliant way of turning a &q... Greg Wooledge

