From: "Yuki Yao" <y_yao@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH]logrotate: /var/log/messages* disappeared
Date: Mon, 8 Feb 2010 11:48:55 +0900 [thread overview]
Message-ID: <000501caa869$41be6670$c53b3350$@co.jp> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2875 bytes --]
Hi,
I found a problem on LTP when I execute ./runltp.
After execute ./runltp, all log files such as /var/log/messages*
disappeared,
and there is only new log files that were created after the test...
This seems a problem that occurs after the "logrotate01" test.
I found that the past log files disappeared by forcing a rotate (logrotate
-fv $LTPTMP/tst_logrotate.conf).
Besides, "logrotate"'s shell script
./testcases/commands/logrotate/logrotate_tests.sh creats
logrotate configuration file ($LTPTMP/tst_logrotate.conf) for the test, and
this config file includes
/etc/logrotate.d as follows:
[ ./testcases/commands/logrotate/logrotate_tests.sh line:156~ ]
----------
# create config file.
cat >$LTPTMP/tst_logrotate.conf <<-EOF
#****** Begin Config file *******
# create new (empty) log files after rotating old ones
create
# compress the log files
compress
# RPM packages drop log rotation information into this
directory
include /etc/logrotate.d
/var/log/tst_logfile {
rotate 5
weekly
}
#****** End Config file *******
EOF
----------
By this, not only a log file for the test (/var/log/tst_logfile), but also
30 fies in my system
such as /var/log/messages* become "logrotate" command target.
Therefore, only a log file for this test must be made a target of the forced
execution of "logrotate".
To resolve this problem, we have to change this not to include
/etc/logrotate.d, I think.
Index: testcases/commands/logrotate/logrotate_tests.sh
==============================
--- logrotate_tests.sh 2008-10-21 15:54:15.000000000 +0900
+++ logrotate_tests.sh.new 2010-02-05 18:56:14.000000000 +0900
@@ -163,7 +163,7 @@
compress
# RPM packages drop log rotation information into this
directory
- include /etc/logrotate.d
+ # include /etc/logrotate.d
/var/log/tst_logfile {
rotate 5
@@ -200,7 +200,7 @@
# check if /etc/logrotate.d is included/
# check if 5 rotations are forced.
# check if compression is done.
- grep "including /etc/logrotate.d"
$LTPTMP/tst_logrotate.out \
+ # grep "including /etc/logrotate.d"
$LTPTMP/tst_logrotate.out \
> $LTPTMP/tst_logrotate.err 2>&1 ||
RC=$?
grep "reading config file
$LTPTMP/tst_logrotate.conf" \
$LTPTMP/tst_logrotate.out >
$LTPTMP/tst_logrotate.err 2>&1 || RC=$?
Thank you,
--Yuki Yao
[-- Attachment #1.2: Type: text/html, Size: 13231 bytes --]
[-- Attachment #2: Type: text/plain, Size: 408 bytes --]
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-02-08 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 2:48 Yuki Yao [this message]
2010-02-08 3:02 ` [LTP] [PATCH]logrotate: /var/log/messages* disappeared Yuki Yao
2010-02-08 6:04 ` Rishikesh
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 8:55 Yuki Yao
2010-02-08 1:33 Yuki Yao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000501caa869$41be6670$c53b3350$@co.jp' \
--to=y_yao@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox