Looks like the server was set to log everything by default (511).
Here's how to change it:
qmgr -c "set server log_events = 127"
Here are the different level descriptions:
1 Error Events
2 Batch System/Server Events
4 Administration Events
8 Job Events
16 Job Resource Usage (hex value 0x10)
32 S
Actually... taking a closer look now- that does appear to be normal. And
I've got similar sizes on my own servers, but a larger /var. ;-) In fact,
it's writing out something on the order of 5MB per day on a 64 node
cluster. I don't want to mandate use of logrotate in the package, as some
us
I've thought about changing PBS's default before and using logrotate, but
even on big iron production systems I've never seen PBS's logfiles get out
of hand... even over years of use. I'll be happy to spend the time
implementing this if there's sufficient need. How large is your /var that
fil
On Thursday 11 March 2004 08:52 pm, Thomas Naughton wrote:
> You might want to checkout LOGROTATE(8).
> --tjn
Thanks for the suggestion.
I know about logrotate, but just for suggestion for OSCAR, it would be even
better if OSCAR manually put this entry in logrotate.conf. I only found out
about
You might want to checkout LOGROTATE(8).
--tjn
_
Thomas Naughton [EMAIL PROTECTED]
Research Associate (865) 576-4184
On Thu, 11 Mar 2004, Jeremy Eno
I doubt you've missed anything. I've not heard of any log expiration
settings for PBS.
Jeremy
At 04:37 PM 3/11/2004, Reuben D. Budiardja wrote:
I just noticed that the master node of our OSCAR cluster is filled up with a
PBS logs in /var/spool/pbs/server_logs. Apparently old logs never
I just noticed that the master node of our OSCAR cluster is filled up with a
PBS logs in /var/spool/pbs/server_logs. Apparently old logs never got
deleted. Is this true in general, or am I missing something ? So we have to
clean this up manually?
RDB
--
Reuben D. Budiardja
Department of Physi
