When I run the logger -p local0.info `date` command, I get nothing -
just returns to the # prompt.

For syslog.conf, I do think I used spaces to separate the
selector/action columns, so I made the change to tab. The line looks
like this:

*.info                                          /tmp

I have issued the svcadm refresh system-log command (we're running
Solaris 10). Would there be anything in the log file if I ran pca.pl
again after this, even though there are no patches that need to be
installed (since I already installed them earlier)? If so, then I'm
still missing something because I tried and I still did not get a
local0.info file.

Jamen McGranahan
Systems Services Librarian
Vanderbilt University

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin Paul
Sent: Monday, December 01, 2008 9:15 AM
To: PCA (Patch Check Advanced) Discussion
Subject: Re: [pca] PCA Forum Link - And question about PCA

McGranahan, Jamen wrote:
> Well, I made the suggested change to syslog.conf to record *.info
files,
> but when I ran pca.pl today and installed 3 patches, I did not get a
> local0.info file as I had expected. Any ideas and/or other
suggestions?

Configuring syslogd can be tricky. Try this command to test you setup:

   logger -p local0.info `date`

Check what you have put into /etc/syslog.conf - make sure you've used a 
TAB and not spaces to separate the selector and action columns. You can 
show us your change to syslog.conf, too.

After modifying syslog.conf, you must tell syslogd to re-read the file. 
Use "pkill -HUP syslogd" under Solaris <=9, or "svcadm refresh 
system-log" on Solaris 10.

In the future, I will probably change the default facility/level used in

pca to something that gets logged by default on a vanilla Solaris system

  (and make syslog logging on by default, too).

Martin.


Reply via email to