> Is this a known bug in klist or is it by design for a script run in a > non-interactive shell?
1. Reference the full path to klist in the script
2. Run it temporarily as '/path/to/klist > /tmp/klist.out 2>&1'
and then examine the /tmp/klist.out file to see what it's
problem is.
________________________________________________
Kerberos mailing list [email protected]
https://mailman.mit.edu/mailman/listinfo/kerberos
