[1128] in arla-drinkers
Re: Odd bug in arla-0.27 on linux (i386) 2.2.12
daemon@ATHENA.MIT.EDU (Love)
Mon Sep 6 05:50:24 1999
From owner-arla-drinkers@stacken.kth.se Mon Sep 06 09:50:24 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 2363 invoked from network); 6 Sep 1999 09:50:23 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 6 Sep 1999 09:50:23 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id LAA02585
for arla-drinkers-list; Mon, 6 Sep 1999 11:41:51 +0200 (MET DST)
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id LAA02581
for <arla-drinkers@stacken.kth.se>; Mon, 6 Sep 1999 11:41:47 +0200 (MET DST)
Received: from hummel.e.kth.se (hummel.e.kth.se [130.237.43.135])
by elixir.e.kth.se (8.9.3/8.9.3) with ESMTP id LAA21838;
Mon, 6 Sep 1999 11:41:40 +0200 (MET DST)
Received: (from lha@localhost)
by hummel.e.kth.se (8.9.3/8.9.3) id LAA01873;
Mon, 6 Sep 1999 11:41:37 +0200 (MET DST)
To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
Cc: Jeffrey Hutzelman <jhutz@cmu.edu>, arla-drinkers@stacken.kth.se
Subject: Re: Odd bug in arla-0.27 on linux (i386) 2.2.12
References: <19990904185954.A1964@afs.mcc.ac.uk> <Pine.SOL.3.95L.990904141818.4071N-100000@afstest-1.fac.cs.cmu.edu> <19990906095852.A2734@afs.mcc.ac.uk>
From: Love <lha@stacken.kth.se>
Date: 06 Sep 1999 11:41:32 +0200
In-Reply-To: Dr A V Le Blanc's message of "Mon, 6 Sep 1999 09:58:52 +0100"
Message-ID: <am906ktm0j.fsf@hummel.e.kth.se>
Lines: 21
User-Agent: Gnus/5.0700000000000003 (Pterodactyl Gnus v0.91) Emacs/20.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Dr A V Le Blanc <LeBlanc@mcc.ac.uk> writes:
> No, I'm just doing a klog. Formerly I had klog as a script that
> just did kauth (or kinit; I forget which), then afslog. Now I'm
> using the new klog from arla, and it doesn't get Kerberos tickets.
The klog seams to just keep the tickets if you give it the option
-tmp. That might change.
> Should it? If it doesn't, then shouldn't the other arla commands
> work by cheking for tokens rather than tickets? Otherwise, shouldn't
> the arla klog get kerberos tickets as well as tokens?
I think it should get tickets and tokens. The tools in arla should check
for both tickets and tokens (in that order). We want to keep compability
with the transarc tools. The general idea is to be better.
Love
