need advise regarding the log rotation, i have the logadm set at
30 2 * * * /usr/sbin/logadm
so it supposed to rotate once per day, but now it rotated twice!
but someone my log will rotate at 2:30 AM, but then another 2 hours later, it creates a new and rotate a new log again, is there anyting wrong or i could check ?
Hello all.
Due to some reason I can not use HUP to rotate needed log files.
So I use the standard method:
cp $file $file.1
cat /dev/null > $file
But if Java application in this time writing the output to $file,
in the beginning of it appears many "^@^@^@^@^@^@".
How to avoid it? Or how... (6 Replies)
I have the below script to help with disk space cleanup that finds logs older than a specified number of days (say 10 days). I need it to grab "active" logs as well. Problem is an "active log" will not get archived unless I put in 0 days which I don't want to do, I need to leave the past 10 days,... (2 Replies)
Hi, I current have many apps servers running and need to create a script to rotate logs daily, and then create an autosys job to delete logs that are older than 30 days. I was thrown into this and have no idea what to do, please help me get started, thanks!
-----Post Update-----
and i will... (6 Replies)
Hi,
Recently i received a request to rotate logs of catalina.out (tomcat). The file size was about 807 MB. I used logadm to truncate the log ( -c ) and zip (-z 0) it.
Everything worked fine, catalina.out.0.gz was created (22 MB) and the size of original catalina.out became 0kb.
After... (2 Replies)
Hi Guys,
Good morning, I just want to know and collect ideas on this one. Regarding rotation of logs as I've observed it's not consistently functioning. I have a server with 8 Partitions, each partition has a dedicated directory for the logs that is needed and I set it every 5mins (300secs) the... (1 Reply)
Hi All!
I seem to have a problem with log rotation, unless I am doing something wrong, I have type the following command for testing purposes to see if the -s option works but he did not:
logadm -w /var/adm/messages -C 8 -c -s 512k -t '/var/adm/messages.$n' -z 1
the file is now at this... (7 Replies)
In Mavericks, Apple has apparently moved control of log rotation to ASL. There's a 'ttl' value to determine how long log files will stick around for. I can compress them, change the way they're named, limit them by size, etc. But the one thing I cannot find is how to NOT keep one log file per... (0 Replies)
Hi All,
I have a situation here ...
HACMP is configured with application monitoring script, which is generating messages .... which is running every minute ...
And every minute when monitoring script run, one one log file is generating .... and this log file is rotating ...
which is rotating... (1 Reply)
Discussion started by: linux.amrit
1 Replies
LEARN ABOUT SUSE
kproplog
kproplog(1M) System Administration Commands kproplog(1M)NAME
kproplog - display the contents of the Kerberos principal update log
SYNOPSIS
/usr/sbin/kproplog [-h | -e num]
DESCRIPTION
The kproplog displays the contents of the Kerberos principal update log to standard output. This command can be used to keep track of the
incremental updates to the principal database, which is enabled by default. The /var/krb5/principal.ulog file contains the update log main-
tained by the kadmind(1M) process on the master KDC server and the kpropd(1M) process on the slave KDC servers. When updates occur, they
are logged to this file. Subsequently any KDC slave configured for incremental updates will request the current data from the master KDC
and update their principal.ulog file with any updates returned.
The kproplog command can only be run on a KDC server by someone with privileges comparable to the superuser. It will display update entries
for that server only.
If no options are specified, the summary of the update log is displayed. If invoked on the master, all of the update entries are also dis-
played. When invoked on a slave KDC server, only a summary of the updates are displayed, which includes the serial number of the last
update received and the associated time stamp of the last update.
OPTIONS
The following options are supported:
-h
Display a summary of the update log. This information includes the database version number, state of the database, the number of
updates in the log, the time stamp of the first and last update, and the version number of the first and last update entry.
-e num
Display the last num update entries in the log. This is useful when debugging synchronization between KDC servers.
-v
Display individual attributes per update. An example of the output generated for one entry:
Update Entry
Update serial # : 4
Update operation : Add
Update principal : test@EXAMPLE.COM
Update size : 424
Update committed : True
Update time stamp : Fri Feb 20 23:37:42 2004
Attributes changed : 6
Principal
Key data
Password last changed
Modifying principal
Modification time
TL data
FILES
/var/krb5/principal.ulog
The update log file for incremental propagation.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWkdcu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO kpasswd(1), gkadmin(1M), kadmin(1M), kadmind(1M), kdb5_util(1M), kprop(1M), kpropd(1M), kadm5.acl(4), kdc.conf(4), attributes(5), SEAM(5)SunOS 5.10 29 Mar 2004 kproplog(1M)