> > I'd suggest just using the IBM binary for the kaserver (and only the
> > kaserver) in your OpenAFS installation
>
> That's an interesting thought, but unfortunately it's nowhere near
> an option. sunx86_ is quite simply not a supported platform for
> IBM AFS at all, even at 3.6 Patch 19 (Aug
Derrick Brashear wrote:
On Tue, Apr 13, 2010 at 4:59 PM, Jacob Ela wrote:
Greetings All,
I've been looking for some information on this because someone else has
probably run into a similar issue, but I haven't found much that is recent or
pointed towards solving the problem - though I've
Derrick,
> I'd suggest just using the IBM binary for the kaserver (and only the
> kaserver) in your OpenAFS installation
That's an interesting thought, but unfortunately it's nowhere near
an option. sunx86_ is quite simply not a supported platform for
IBM AFS at all, even at 3.6 Patch 19 (August
On Apr 14, 2010, at 11:23 AM, Jeffrey Altman wrote:
> On 4/14/2010 10:51 AM, Steve Simmons wrote:
>>
>> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>>
I'm a long-time fan of having a switch that causes tools to dump their
data in an easy-to-machine-parse format. That isn
Hi,
On Wed, Apr 14, 2010 at 11:23:17AM -0400, Jeffrey Altman wrote:
[snip]
> >>> I'm a long-time fan of having a switch that causes tools to dump their
> >>> data in an easy-to-machine-parse format. That isn't always doable, but
> >>> when it is, it's a big win.
[snip]
> Anyone want a -xml opt
Hey GSoC candidates! here's a simple project for you. vos examine
already includes a "-format" switch to display a fixed, parseable
format. add a "-xml" switch, and output in xml! Everything you need to
change is in src/volser (vos.c and vsprocs.c). Ideally you won't
require an external library to
On 2010-04-14 at 11:23, Jeffrey Altman ( jalt...@secure-endpoints.com ) said:
On 4/14/2010 10:51 AM, Steve Simmons wrote:
On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
I'm a long-time fan of having a switch that causes tools to dump their data in
an easy-to-machine-parse format. That i
On Wed, Apr 14, 2010 at 11:23 AM, Jeffrey Altman
wrote:
> On 4/14/2010 10:51 AM, Steve Simmons wrote:
>>
>> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>>
I'm a long-time fan of having a switch that causes tools to dump their
data in an easy-to-machine-parse format. That isn
On 4/14/2010 10:51 AM, Steve Simmons wrote:
>
> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>
>>>
>>> I'm a long-time fan of having a switch that causes tools to dump their data
>>> in an easy-to-machine-parse format. That isn't always doable, but when it
>>> is, it's a big win.
>>
>> As
I'd suggest just using the IBM binary for the kaserver (and only the
kaserver) in your OpenAFS installation (or better yet switching to
krb5)
On Wed, Apr 14, 2010 at 6:10 AM, Atro Tossavainen
wrote:
> OK, I have it again. User reports inability to log in.
>
> $ kas -a dsakfksda
> Administrator's
On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>>
>> I'm a long-time fan of having a switch that causes tools to dump their data
>> in an easy-to-machine-parse format. That isn't always doable, but when it
>> is, it's a big win.
>
> As Andrew pointed out in another reply in this thread, t
On Apr 13, 2010, at 7:02 PM, Derrick Brashear wrote:
>> Has anyone run into something like this? Is there a way to change the
>> permissions AFS reports to OSX, or is there a work around I'm failing to see?
>
> Check out the RealModes setting. Edit
> /var/db/openafs/etc/config/settings.plist,
Rainer,
> One of your DB servers has an incorrect /usr/afs/etc/KeyFile (in
> Transarc-naming, if you use the /var/openafs style it's accordingly).
>
> Very likely you added a new key but did not propagate the KeyFile everywhere.
> "bos listkey " should help.
According to bos listkey of the vari
Atro Tossavainen schrieb:
OK, I have it again. User reports inability to log in.
$ kas -a dsakfksda
Administrator's (dsakfksda) Password:
ka> exa useraccount
examine: ticket contained unknown key version number getting information for
useraccount.
One of your DB servers has an incorrect /
OK, I have it again. User reports inability to log in.
$ kas -a dsakfksda
Administrator's (dsakfksda) Password:
ka> exa useraccount
examine: ticket contained unknown key version number getting information for
useraccount.
So:
$ udebug 128.214.88.114 7004 -long
Host's addresses are: 128.214.88
15 matches
Mail list logo
