[an error occurred while processing the directive]

	cosign-discuss at umich.edu
	general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where does cosign write its log(s)? <EOM>

To: Wesley Craig <wes@xxxxxxxxx>
Subject: Re: Where does cosign write its log(s)? <EOM>
From: Jonathan Maybaum <maybaum@xxxxxxxxx>
Date: Fri, 12 Aug 2005 16:29:08 -0400
Cc: cosign-discuss Discussion <cosign-discuss@xxxxxxxxx>
In-reply-to: <33C7540A-58EF-4157-944F-9E16EFF51F84@umich.edu>
References: <80003447-0656-429B-982E-63532DB7ECA3@umich.edu> <F673F0D7-83C1-412C-9586-422A3FE9CD0A@umich.edu> <33C7540A-58EF-4157-944F-9E16EFF51F84@umich.edu>

Well, I see mostly entries like: Aug 12 15:35:22 maybaum-med-umich-edu kernel[0]: cosignd[223] uses send/recv on a pipe

This does not appear to be helpful in diagnosing problems, though.

--JM

On Aug 12, 2005, at 2:54 PM, Wesley Craig wrote:

On 12 Aug 2005, at 10:34, johanna bromberg craig wrote:

The default location is whatever you have defined as LOG_DAEMON ( likely daemon ) This is set in this line of the Makefile COSIGNSYSLOG=LOG_DAEMON And can be overridden with command line option -F.

Another way of saying this: cosignd writes it's logs with syslog. syslog on Mac OS X might not be putting these where you expect. Check out /etc/syslog.conf.

:wes

References:
- Where does cosign write its log(s)? <EOM>
  - From: Jonathan Maybaum
- Re: Where does cosign write its log(s)? <EOM>
  - From: johanna bromberg craig
- Re: Where does cosign write its log(s)? <EOM>
  - From: Wesley Craig

Prev by Date: RE: IISCosign - one physical server more than 1 cosign-servicepossible?
Next by Date: RE: IISCosign - one physical server more than 1cosign-servicepossible?
Previous by thread: Re: Where does cosign write its log(s)? <EOM>
Next by thread: Where files are placed
Index(es):
- Date
- Thread

[an error occurred while processing the directive]