Well i have OpenAFS working on OpenSI for a while now.
Things seem to work pretty stable, however we needed a "hack" in some SSI
filesystem handling when
a process migrates to another clusternode.
We think we have a good solution for it instead of just a hack.
the question is, does AFS have a u
There are no compiled locale specific message files for the logging
data generated by OpenAFS for Windows.
Therefore the log entries appear as they do.
Jeffrey Altman
Gurganus, Brant L wrote:
That is a detail that is part of the event meant to replace a %1 in the actual
message such a
That is a detail that is part of the event meant to replace a %1 in the actual
message such as
File not found: %1
Where %1 would change for each time the message occurs. In this case, the
message sounds like it is supposed to be "AFS running," but instead of giving
that as the message it is giv
Gurganus, Brant L wrote:
> There are AFS Client entries that appear in the Application event log
> that do not contain their message. What are the messages supposed to be
> and why are they not appearing?
They do include the message:
"AFS running."
smime.p7s
Description: S/MIME Cryptographic S
There are AFS Client entries that appear in the Application
event log that do not contain their message. What are the messages supposed to
be and why are they not appearing?
Event Type: Information
Event Source: AFS Client
Event Category: None
Event ID: 0
David Sonenberg <[EMAIL PROTECTED]> writes:
> What about interoperability with 1.2.13? Can I migrate the 3 servers
> one at a time or will running different versions create problems?
I had a cell with one server at 1.2.13 and three servers at various versions
of 1.3.x up to 1.4rc4 running for ab
In message <[EMAIL PROTECTED]>,Loic Tortay writes:
>Indeed, the 1.4.0 release doesn't work in 64 bit mode even when
>clearing the cache.
well i cant seem to spot what is going wrong. there doesnt seem to
anyway that AFSFetchStatus->Length_hi could be left unintialized.
so, could you try a couple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Sonenberg wrote:
> What about interoperability with 1.2.13? Can I migrate the 3 servers
> one at a time or will running different versions create problems?
As far as I know, they work together with no prob.
Running different versions should not
What about interoperability with 1.2.13? Can I migrate the 3 servers
one at a time or will running different versions create problems?
Lars Schimmer wrote:
> I assume 1.2.13 and 1.4.0 will work flawless together in a network.
> So just migrate one after another.
> And: there is no need to conver
According to chas williams - CONTRACTOR:
[...]
>
> so, just to be certain about some things, the 1.4.0 release is broken
> right (even after clearing the cache)? and specifically, what options do
> you pass to afsd?
>
Indeed, the 1.4.0 release doesn't work in 64 bit mode even when
clearing the cac
10 matches
Mail list logo
