On Mar 14, 2006, at 7:37 PM, Russ Allbery wrote:
Okay, so let's get some consensus on what we're going to implement
before
anyone writes code. It sounds like what people want are:
* The current date format.
* -mm-dd
* -mm-dd hh:mm[:ss][-/+]
* -mm-ddThh:mm[:ss][-/+]
Yes, I think someone should code this up. There is no need for
afs_strptime, just put our own strptime inside of #ifndef HAVE_STRPTIME
(with appropriate configure code). See util/strl*.c.
The OpenBSD version of strptime still has the dreaded advertising clause, so
I have not imported it. Maybe
On Wed, 15 Mar 2006, Jim Rees wrote:
Yes, I think someone should code this up. There is no need for
afs_strptime, just put our own strptime inside of #ifndef HAVE_STRPTIME
(with appropriate configure code). See util/strl*.c.
The OpenBSD version of strptime still has the dreaded advertising
Jim Rees [EMAIL PROTECTED] writes:
Yes, I think someone should code this up. There is no need for
afs_strptime, just put our own strptime inside of #ifndef HAVE_STRPTIME
(with appropriate configure code). See util/strl*.c.
The OpenBSD version of strptime still has the dreaded advertising
On Wed, 15 Mar 2006, Jim Rees wrote:
That won't help. Theo already went on a quest to remove the licensing
clause wherever possible. The strptime license is from Powerdog Industries,
not Berkeley. It originally had a much more restrictive license that didn't
even allow modification, and
On Wednesday, March 15, 2006 02:51:22 PM -0500 Derrick J Brashear
[EMAIL PROTECTED] wrote:
On Wed, 15 Mar 2006, Jim Rees wrote:
That won't help. Theo already went on a quest to remove the licensing
clause wherever possible. The strptime license is from Powerdog
Industries, not Berkeley.
On Wed, 15 Mar 2006, Jeffrey Hutzelman wrote:
http://developer.berlios.de/projects/uuu/ looks like it has one with a
BSD non-advertising-clause license.
Someone want to confirm?
I'd love to, if I didn't have to manually search an entire complex CVS
repository looking for the file that might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I've got this error today:
vos: failed to parse date '13/03/2006' (error=-2))
in a
vos dump -id user.schimmer.backup -time 13/03/2006 -file
/backup/user.schimmer.backup.dump.14.03.2006 localauth
commandline.
Does this error tells me, there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lars Schimmer wrote:
Hi!
I've got this error today:
vos: failed to parse date '13/03/2006' (error=-2))
I've got the solution via email:
I switched the date/month field.
Thx so far.
MfG,
Lars Schimmer
- --
-
Dates in the form xx/yy/ are ambiguous and should probably be avoided.
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Rees wrote:
Dates in the form xx/yy/ are ambiguous and should probably be avoided.
And what is the official way without these to do incremental dumps of a
volume?
Cya,
Lars Schimmer
- --
-
It looks like this is the only format vos -time understands. Can anyone
think of a reason not to fix this?
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
Jim Rees [EMAIL PROTECTED] writes:
It looks like this is the only format vos -time understands. Can anyone
think of a reason not to fix this?
Not I. -MM-DD is generally the best date format to use, since I think
it's unambiguous in pretty much every country. It should be fairly easy
to
How widely is strptime implemented? If all our supported platforms have it,
that would make things easier. It's in all the BSDs.
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
Jim Rees [EMAIL PROTECTED] writes:
How widely is strptime implemented? If all our supported platforms have
it, that would make things easier. It's in all the BSDs.
It's not in the list of functions I trust to exist, but it's at least
present on Linux, Solaris 8, and AIX 5.2. I no longer
On Tue, 14 Mar 2006, Russ Allbery wrote:
Jim Rees [EMAIL PROTECTED] writes:
How widely is strptime implemented? If all our supported platforms have
it, that would make things easier. It's in all the BSDs.
It's not in the list of functions I trust to exist, but it's at least
present on
Russ Allbery wrote:
Jim Rees [EMAIL PROTECTED] writes:
How widely is strptime implemented? If all our supported platforms have
it, that would make things easier. It's in all the BSDs.
It's not in the list of functions I trust to exist, but it's at least
present on Linux, Solaris 8, and
It's not in the list of functions I trust to exist, but it's at least
present on Linux, Solaris 8, and AIX 5.2. I no longer have IRIX or HP-UX
to check.
I see it on an HPUX 11.00 box.
If not strptime(), then at least time since the epoch please.
steve
- - -
systems network manager
My old HP 10.0 book of man pages says:
Author
strptime{} was developed by OSF and HP.
Standards Compliance
strptime: XPG4
Russ Allbery wrote:
Jim Rees [EMAIL PROTECTED] writes:
How widely is strptime implemented? If all our supported platforms have
it, that would make
On Tue, 14 Mar 2006, Jim Rees wrote:
It looks like this is the only format vos -time understands. Can anyone
think of a reason not to fix this?
When you say fix, do you mean to change the current behavior?
Or do you mean to add additional formatting options?
Changing the current behavior
* Russ Allbery [2006-03-14 09:46:30 -0800]:
Jim Rees [EMAIL PROTECTED] writes:
It looks like this is the only format vos -time understands. Can anyone
think of a reason not to fix this?
Not I. -MM-DD is generally the best date format to use, since I think
it's unambiguous in
Sergio Gelato [EMAIL PROTECTED] writes:
[...]
I also second the suggestion of accepting seconds since the UNIX epoch:
it's what AFS uses internally, including in the dump file format. If one
wants to base the start time for an incremental dump on the time of a
previous dump (which is stored
22 matches
Mail list logo
