Problems with barf and non-file logs

-----BEGIN PGP SIGNED MESSAGE-----

  This is an annoying problem, some asshole in Linux land has put a
named pipe as a file in /var/log!  Ghods knows what reason the fool
might have had, but he sure never had to sysadmin a real Unix box...

  So along comes me and the simple "ipsec barf" command that foolishly
expects files in /var/log and the egrep locks up on this fools named
pipe stuck in the wrong place (/var/log/popauth).  Our code locks up
and gets blamed.  Sigh, we should be more robust.

  Now I don't know if there is a way to check to see if a file is a
pipe before trying to grep it, and if there were it just might be
related to crypto somehow and I could not tell you folks about it...
but we do need to check files to be sure they are not dirs or pipes
it seems.

  Either that or just do a forced delete the fools pipe...  Sigh, much
as it appeals to me at the moment it's not a good way to play with
others.

		||ugh

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: For the matching public key, finger the Reply-To: address.

iQCVAwUBPj8yXFZpdJR7FBQRAQE1PgP8DssqzqlgB7VXiLPormjjRu2LaHTRb3PM
C953a27GZWJjKhOKLtcZwDMyLS4ZDg/Jy13SC2QKTLNrnPGdMLLt6vxpuqjVmFj7
iPo8gz5Ptzigm+IPWmbTMpJsNm0xm6VaQrWu0uqKtJ4p7AE+SISkdIY0bUyTCrPp
ajboPbqrle8=
=0FuL
-----END PGP SIGNATURE-----