I tried to use GDB but it would appear that the symbols are stripped from the crond binary, as the backtrace only provided the following:
I HUPed the cron daemon, and waited to see if the test script ran, but unfortunately no... even though it is theoretically writing to someplace other than the /var partition (aka. /tmp)
As for strace, I was unaware that I could attach strace to a process that is already running... if that is so, can you reference an example? I will gladly kick it off as a test.
Hi all,
I have configured logrotate to logorotate every 12 hour. The configurations are as follows.
/etc/cron.d/config
-------------------------
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
HOME=/root
0 */12 * * * root logrotate /etc/logrotate.d/test
... (1 Reply)
Hi there,
I want to rotate the logfiles which are located in /var/log/jboss/tomcat*
so I have created a file named as 'tomat' in /etc/logrotate.d/tomcat with the following content.
# cat /etc/logrotate.d/tomcat
/var/log/jboss/tomcat_access_log*.log {
daily
nocreate
... (2 Replies)
Hi,
I have the following configuration file:
/logs/system/mindundi/* {
rotate 0
daily
missingok
sharedscripts
postrotate
find /logs/system/mindundi/ -name "*log" -mtime +15 -exec /bin/rm -f {} \;
endscript
}
I want to save only... (6 Replies)
Hi guys,
I've got two separate logrotates I'd like to run, one for Tomcat and one for Apache, but I'd like to run the Tomcat one daily and the Apache one weekly. Now, the logrotate itself is working fine, but although I have 'daily' in Tomcat, and 'weekly' in the Apache one, the latter is... (2 Replies)
I have written script which is working in Home directory perfectly and also compressing log files and rotating correctly. But, when i try to run script for /var/log/ i am able to get compressed log files but not able to get rotation of compressed log files. Please suggest.
I am using below command... (5 Replies)
Hi Admins.
I have installed logrotate rpm on Aix 6.1.
After the installation of rpm, I don't find /etc/logrotate.conf file and /etc/logrotate.d dir .
The config file is located in /opt/freeware/etc/logrotate.conf.
When I ran
logrotate -v /opt/freeware/etc/logrotate.conf
I get below... (2 Replies)
Hi, I have a problem with logrotate at Centos 7.
My logrotate is configured with "rotate 0" to Apache logs, so it should never keep logs when rotating, just removing them and replacing by new empty ones at every rotation. But for some reason, once in a while, I see that logrotate is creating... (0 Replies)
Guys, is there a script or command?
how to disable cron emails, but only for logrotate only not for other logs (3 Replies)
Discussion started by: kenshinhimura
3 Replies
LEARN ABOUT SUNOS
strace
strace(1M) System Administration Commands strace(1M)NAME
strace - print STREAMS trace messages
SYNOPSIS
strace [ mid sid level...]
DESCRIPTION
strace without arguments writes all STREAMS event trace messages from all drivers and modules to its standard output. These messages are
obtained from the STREAMS log driver (see log(7D)). If arguments are provided, they must be in triplets of the form mid, sid, level, where
mid is a STREAMS module ID number, sid is a sub-ID number, and level is a tracing priority level. Each triplet indicates that tracing
messages are to be received from the given module/driver, sub-ID (usually indicating minor device), and priority level equal to, or less
than the given level. The token all may be used for any member to indicate no restriction for that attribute.
The format of each trace message output is:
<seq> <time> <ticks> <level> <flags> <mid> <sid> <text>
<seq> trace sequence number
<time> time of message in hh:mm:ss
<ticks> time of message in machine ticks since boot
<level> tracing priority level
<flags> E : message is also in the error log F : indicates a fatal error N : mail was sent to the system administrator (hardcoded
as root)
<mid> module ID number of source
<sid> sub-ID number of source
<text> formatted text of the trace message
Once initiated, strace will continue to execute until terminated by the user.
EXAMPLES
Example 1: A sample output of the strace command:
The following example outputs all trace messages from the module or driver whose module ID is 41:
strace 41 all all
The following example outputs those trace messages from driver or module ID 41 with sub-IDs 0, 1, or 2:
strace 41 0 1 41 1 1 41 2 0
Messages from sub-IDs 0 and 1 must have a tracing level less than or equal to 1. Those from sub-ID 2 must have a tracing level of 0.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO attributes(5), log(7D)
STREAMS Programming Guide
NOTES
o There is no restriction to the number of strace processes opening the STREAMS log driver at a time.
o The log-driver records the list of the triplets specified in the command invocation, and compares each potential trace message against
this list to decide if it should be formatted and sent up to the strace process. Hence, long lists of triplets will have a greater
impact on overall STREAMS performance. Running strace will have the most impact on the timing of the modules and drivers generating
the trace messages that are sent to the strace process. If trace messages are generated faster than the strace process can handle
them, some of the messages will be lost. This last case can be determined by examining the sequence numbers on the trace messages
output.
SunOS 5.10 4 Oct 1994 strace(1M)