[1131] in arla-drinkers

home help back first fref pref prev next nref lref last post

Re: Odd bug in arla-0.27 on linux (i386) 2.2.12

daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Tue Sep 7 13:56:43 1999

From owner-arla-drinkers@stacken.kth.se Tue Sep 07 17:56:41 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 13591 invoked from network); 7 Sep 1999 17:56:40 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 7 Sep 1999 17:56:40 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id TAA19438
	for arla-drinkers-list; Tue, 7 Sep 1999 19:47:50 +0200 (MET DST)
Received: from minbar.fac.cs.cmu.edu (MINBAR.FAC.CS.CMU.EDU [128.2.185.161])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with SMTP id TAA19432;
	Tue, 7 Sep 1999 19:47:45 +0200 (MET DST)
Received: from AFSTEST-2.FAC.CS.CMU.EDU by minbar.fac.cs.cmu.edu id aa15629;
          7 Sep 99 13:47 EDT
Date: Tue, 07 Sep 1999 13:33:17 -0400
From: Jeffrey Hutzelman <jhutz+@cmu.edu>
To: Love <lha@stacken.kth.se>
cc: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>, arla-drinkers@stacken.kth.se
Subject: Re: Odd bug in arla-0.27 on linux (i386) 2.2.12
Message-ID: <408326482.936711197@AFSTEST-2.FAC.CS.CMU.EDU>
In-Reply-To: <am906ktm0j.fsf@hummel.e.kth.se>
Originator-Info: login-token=Mulberry:01AoWrgmztIPZO0CoFRwcc5I3qF69E/jN4sw71AvMnCwL4EfM=;
 token_authority=postmaster@andrew.cmu.edu
X-Mailer: Mulberry (Win32) [1.4.4, s/n S-100002]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

>> 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.

.. without being incompatible.  Transarc's "klog" doesn't mess with your
ticket file unless you tell it to.  Besides being "compatible", this is
also "right" -- klog has no business messing with my ticket file (unless,
perhaps, I tell it to).

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA


home help back first fref pref prev next nref lref last post