Derek Atkins <[EMAIL PROTECTED]> writes:
> Set your krb.conf/krb5.conf to point to the new KDC.
>
> Or do you mean you're actually using "klog"???
Windows client uses the db server as kerberos servers (and so does klog)
I use a udp forwarder to that I wrote to "solve" the problem.
ftp://ftp.sta
"James D. Nurmi" <[EMAIL PROTECTED]> writes:
> the krb5.conf is correctly stating that the kdc & adminserver are the
> newly CNamed kerberos1 machine... Kinit works, aklog works. klist
> lists out the new ticket, tokens claims to have tokens... However if I
> try to enter a section on /afs that r
On Mon, 2003-02-24 at 03:09, Hartmut Reuter wrote:
> Norman P. B. Joseph schrieb:
> > I have a replicated volume (on the same server and partition as its RW
> > volume) that won't attach, and won't respond to salvaging. Here's the
> > SalvageLog entry when salvaging the single volume:
> >
> > # b
HAH! Got the bugger The latest error was because I still had an
afs/cellname principal running around... So the fix is either tweak
krb5.conf to default to afs/cellname (or just afs) (windows clients
wont go to afs/cellname, at least not that I've found, so my choice was
straight [EMAIL
On 25 Feb 2003, Norman P. B. Joseph wrote:
> Not that I doubt your diagnosis, Harmut, (and thanks for the response),
> but "c2t0d2s6" is a long name? And anyways, it seems long past the time
> that we should be expecting dynamically generated pathnames fit into
> fixed-length buffers. Regardless
On Tue, 2003-02-25 at 13:12, Derrick J Brashear wrote:
>
> If you roll over the pid space so you're using <= 4 digit pids, what
> changes?
>
> I'm not kidding.
You anticipated my response nicely. :^) But even a 2-digit PID fails:
# bos salvage sun43 s 536871053 -show
Starting salvage.
bos: w
On 25 Feb 2003, Norman P. B. Joseph wrote:
> 02/25/2003 13:35:23 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager /viceps
> 536871053)
> 02/25/2003 13:35:34 Scanning inodes on device /dev/rdsk/c2t0d2s6...
> 02/25/2003 13:36:01 No applicable vice inodes on c2t0d2s6; not salvaged
> Temporary file /
Hi -
You might find that salvaging ANY readonly volume will return the same
message about
No applicable inodes
Temp file missing
I believe that the salvager automatically skips doing anything with
readonly volumes.
Thanks
Todd
___
Op
Assuming that to be the case, how do I recover? Is it as simple as
adding "-force" to the salvage command, or am I misreading what the
effect of the "-force" option is meant to be?
Thanks,
-norm
On Tue, 2003-02-25 at 14:05, [EMAIL PROTECTED] wrote:
> Hi -
>
> You might find that salvaging AN
This is interesting. The salvager appears to unlink the file in a child
process, then try to open it again later in the parent (am I reading
this correctly?):
# fgrep salvage.inodes /tmp/salvager.truss.log
159:open("/viceps/salvage.inodes.c2t0d2s6.159", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 8
159
The last time this happened to me (solaris 8 running transarc 3.6 2.26), I
found that salvaging the problem volume alone wasn't enough I even
tried specifiying "-tmpdir /tmp -orphans remove" without success.
What finally worked for me was salvaging the entire partition housing the
problem vol
Hi -
What happens when you try to do the following:
- vos remsite -server -part \
-id
- vos zap -server -part \
-id -force
try leavng off force first if you want to.
I'm not sure if you tried this yet or not.
Thanks
Todd
___
Is "vos zap" a good idea when the read-write is there too? I seem to
recall getting bitten doing this, damaging the RW copy as well as
removing the broken RO. Of course this was probably AFS 3.3 or 3.4, so
things may have changed since then.
If the RW is still there, I'd recommend:
"vos remsite
Salvaging the entire partition had no effect.
-norm
On Tue, 2003-02-25 at 14:24, Stephen Joyce wrote:
> The last time this happened to me (solaris 8 running transarc 3.6 2.26), I
> found that salvaging the problem volume alone wasn't enough I even
> tried specifiying "-tmpdir /tmp -orphans
On Tue, 2003-02-25 at 14:43, Broughton, Travis V wrote:
> If the RW is still there, I'd recommend:
>
> "vos remsite" on the broken RO, then move the RW somewhere else, then
> zap the broken RO, then add another RO instance and release.
Well, that, indeed, solved it. Though I'm no closer to unde
On Tue, 2003-02-25 at 18:03, Joseph H Vilas wrote:
> Ruby <[EMAIL PROTECTED]> mentioned:
>
> > Maybe you refer to the limited token life time? That can be fixed by
>
> [...]
>
> > ip based ACLs.
>
> I got tired of figuring this out and explaining it, so I wrote:
>
> http://www.
Could this be used to to let the users in my cell use ssh-keys against a
cvs-server? I've been trying to get key-authentication working, but I've
failed miserably... ;)
I think what you really want is afs token passing. The OpenBSD version of
OpenSSH can do this. I'm not sure about the por
17 matches
Mail list logo
