All:
I think I went astray during some of the re-trials that I tried to
preform. I have reinstalled the primary packages and gotten to the
same stage as before. Although the error message remains, the same,
aklog appears to resolve the name correctly to the ID:
# aklog -d node30.emergen.biz -k
-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
is there any reason that the dump to a pipe would be less reliable then the
dump to a file?
apologies for the wasted bandwidth and time, there were unrelated other
problems with the box
that i was not aware of. it works now.
also, does a volume read-only snapshot have to be created on the
-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
The fileserver crashes on amd64_linux2[46] (and probably also
ia64_linux2[46]) when tracing is turned on (TSTP signal).
The reason: inet_ntoa() is not declared anywhere and therefore assumed
returning an int, but the format string in ViceLog expects a char *
(which on some architectures are
I'm opposed to nested includes because it makes it difficult to diagnose
include ordering violations but I realize that's a losing battle.
I actually wonder why hardly anybody uses the '%I' format instead
which util/snprintf.c understands - perhaps because a move to IPv6 (if
ever) would
my odyssey with openafs / kerberos for windows continues.
recall from last time, i had managed to actually get openafs 1.4.0 +
KfW 3.0.0 working. nominally... more working than not, at least. 95%
working, say.
now, also recalling from last time, i mentioned a strange issue: after
you install KfW
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
Hi folks, I'm new to this whole AFS thing, so please forgive if I'm
doing something wrong. To start, I'm running OpenAFS 1.5.0 (though I
was experiencing this problem with 1.4.0, too). Both my test machines
are Windows XP SP2 in this case (though the server is running in a
VMWare window).
I'm
Hello,
I just received a shining MacBook Pro, but I see that RC8 (working
pretty well with 10.4 on the PPC platform) gives kernel extension
errors. I tried the RC9, but the binary distribution seems bugged (it
removes aklog without a substitution, so that no tokens are
available). There
Chris Wagner [EMAIL PROTECTED] writes:
Hi folks, I'm new to this whole AFS thing, so please forgive if I'm
doing something wrong. To start, I'm running OpenAFS 1.5.0 (though I
was experiencing this problem with 1.4.0, too). Both my test machines
are Windows XP SP2 in this case (though the
On Tue, 14 Mar 2006, Alberto Paoluzzi wrote:
Hello,
I just received a shining MacBook Pro, but I see that RC8 (working pretty
well with 10.4 on the PPC platform) gives kernel extension errors. I tried
the RC9, but the binary distribution seems bugged (it removes aklog without a
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
The Account Manager is a tool for managing accounts in kaserver.
It would not be used for managing accounts in a Kerberos KDC or
in Active Directory. It is my hope that one day the Account
Manager could be modified to support the MIT and Heimdal kadmin
protocols as well as LDAP for Active
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
I've tested this a bunch in the past and never had issues, but now I've
got a real restore request and naturally things aren't behaving:
Running OpenAFS 1.4.0 on Linux 2.4.26 #1 SMP Tue Oct 12 14:43:35 EDT
2004 i686 unknown.
backup volrestore afsfs1.ssg.gmu.edu vicepa -volume
Thanks Steve.
Does this mean that this feature is considered experimental at this
point? Do any binary builds support it by default?
Thanks,
Josh
From: Steve Devine [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 10:16 AM
To: Pullen, Josh
Cc:
On Mar 14, 2006, at 3:15 PM, Jim Rees wrote:
Maybe you're hitting the limit on volume name length? If so that's a
poor
error message you're getting.
That gets me closer -- my count was off by 1 character. Now I get a
segfault...
Tape mount callout routine is
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
28 matches
Mail list logo
