| Date: | Thu, 22 Feb 2007 15:05:03 -0800 (Pacific Standard Time) |
| From: | petesea@bigfoot.com |
| Subject: | KfW 3.1: stderr of kinit/klist/kdestroy cannot be re-directed to file |
| To: | kfw-bugs@mit.edu |
Error output from kinit/klist/kdestroy will display a Windows dialog if
stderr is re-directed to a file.
Running this from a DOS command prompt returns stderr to the DOS command
window (as I would expect):
C:\> klist -c foobar
klist: No credentials cache found (ticket cache API:foobar)
But if stderr is re-directed to a file, it displays a Windows dialog
instead and nothing goes to the file:
C:\> klist -c foobar 2> err.log
(dialog with OK button -- same error as above)
(err.log is empty)
Re-directing stdout (assuming the command did not return an error) seems to
work fine, but re-directing stderr doesn't.
This makes it very difficult to log error messages if kinit/klist/kdestroy
are run from a background job, and therefore very difficult to diagnose
problems.
stderr is re-directed to a file.
Running this from a DOS command prompt returns stderr to the DOS command
window (as I would expect):
C:\> klist -c foobar
klist: No credentials cache found (ticket cache API:foobar)
But if stderr is re-directed to a file, it displays a Windows dialog
instead and nothing goes to the file:
C:\> klist -c foobar 2> err.log
(dialog with OK button -- same error as above)
(err.log is empty)
Re-directing stdout (assuming the command did not return an error) seems to
work fine, but re-directing stderr doesn't.
This makes it very difficult to log error messages if kinit/klist/kdestroy
are run from a background job, and therefore very difficult to diagnose
problems.