From: Scott Wiersdorf <scott@bluehost.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
matt@bluehost.com
Subject: Re: [PATCH 2.6.25-4] getdelays.c: signal handling for log rotation
Date: Fri, 6 Jun 2008 14:40:06 -0600 [thread overview]
Message-ID: <20080606204005.GA4283@perlcode.org> (raw)
In-Reply-To: <4848B305.9080305@linux.vnet.ibm.com>
On Fri, Jun 06, 2008 at 09:16:13AM +0530, Balbir Singh wrote:
> > #define PRINTF(fmt, arg...) { \
> > @@ -80,6 +81,7 @@ static void usage(void)
> > fprintf(stderr, " -l: listen forever\n");
> > fprintf(stderr, " -v: debug on\n");
> > fprintf(stderr, " -C: container path\n");
> > + fprintf(stderr, "\nSend USR1 to reopen the logfile if -w is used.\n");
>
> Please mention that old data will be lost and that SIGUSR1 will take affect
> after some data is received.
See below.
> Aren't we better of using the newer sigaction primitives? IIRC, signal can be
> racy. The man page states "Avoid its use"
I've rewritten this to use the new sigaction (bottom of this email). Thanks!
> > +int reopen_logfile(int fd, char *logfile)
> > +{
> > + if (fd) {
> > + PRINTF("USR1 received. Closing logfile.\n");
> > + close(fd);
> > + }
> > + fd = open(logfile, O_WRONLY | O_CREAT | O_TRUNC,
> > + S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
>
> So sending USR1 causes data to be lost?
Yes, if you don't move the old file out of the way first. Sending a
USR1 can also be used to rotate the log:
# ./getdelays -m0,1 -l -w logfile &
(time passes)
# mv logfile logfile.0
# kill -USR1 <pid>
Or to truncate the log:
# ./getdelays -m0,1 -l -w logfile &
(time passes)
# kill -USR1 <pid>
> > + if (reopen_log) {
> > + fd = reopen_logfile(fd, logfile);
> > + }
>
> This seems way of the 80 character space. You have braces that are not required.
Yeah, I'm all for saving one line ;-) (fixed in this new patch)
Signed-off-by: Scott Wiersdorf <scott@perlcode.org>
---
--- Documentation/accounting/getdelays.c 2008-05-15 09:00:12.000000000 -0600
+++ Documentation/accounting/getdelays.c 2008-06-06 14:34:37.000000000 -0600
@@ -50,6 +50,8 @@ int dbg;
int print_delays;
int print_io_accounting;
int print_task_context_switch_counts;
+volatile sig_atomic_t reopen_log;
+struct sigaction sig_usr1;
__u64 stime, utime;
#define PRINTF(fmt, arg...) { \
@@ -80,6 +82,8 @@ static void usage(void)
fprintf(stderr, " -l: listen forever\n");
fprintf(stderr, " -v: debug on\n");
fprintf(stderr, " -C: container path\n");
+ fprintf(stderr, "\nSend USR1 to reopen and truncate the logfile (if \
+-w is used). New log is\ncreated after next netlink datum is received.\n");
}
/*
@@ -231,6 +235,30 @@ void print_ioacct(struct taskstats *t)
(unsigned long long)t->cancelled_write_bytes);
}
+void catch_usr1(int sig)
+{
+ reopen_log = 1;
+ sigaction(SIGUSR1, &sig_usr1, NULL);
+}
+
+int reopen_logfile(int fd, char *logfile)
+{
+ if (fd) {
+ PRINTF("USR1 received. Closing logfile.\n");
+ close(fd);
+ }
+ fd = open(logfile, O_WRONLY | O_CREAT | O_TRUNC,
+ S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
+ if (fd == -1) {
+ perror("Cannot open output file\n");
+ exit(1);
+ }
+
+ reopen_log = 0;
+
+ return fd;
+}
+
int main(int argc, char *argv[])
{
int c, rc, rep_len, aggr_len, len2, cmd_type;
@@ -320,12 +348,11 @@ int main(int argc, char *argv[])
}
if (write_file) {
- fd = open(logfile, O_WRONLY | O_CREAT | O_TRUNC,
- S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
- if (fd == -1) {
- perror("Cannot open output file\n");
- exit(1);
- }
+ fd = reopen_logfile(fd, logfile);
+ sig_usr1.sa_handler = catch_usr1;
+ memset (&sig_usr1.sa_mask, 0x00, sizeof(sigset_t));
+ sig_usr1.sa_flags = SA_RESTART;
+ sigaction(SIGUSR1, &sig_usr1, NULL);
}
if ((nl_sd = create_nl_socket(NETLINK_GENERIC)) < 0)
@@ -444,6 +471,8 @@ int main(int argc, char *argv[])
err(1,"write error\n");
}
}
+ if (reopen_log)
+ fd = reopen_logfile(fd, logfile);
if (!loop)
goto done;
break;
next prev parent reply other threads:[~2008-06-06 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 19:43 [PATCH 2.6.25-4] getdelays.c: signal handling for log rotation Scott Wiersdorf
2008-06-06 3:46 ` Balbir Singh
2008-06-06 20:40 ` Scott Wiersdorf [this message]
2008-06-06 13:59 ` Andi Kleen
2008-06-06 20:42 ` Scott Wiersdorf
2008-06-07 1:10 ` Andi Kleen
2008-06-06 20:47 ` Scott Wiersdorf
2008-06-07 1:13 ` Andi Kleen
2008-06-09 14:20 ` Scott Wiersdorf
2008-06-09 14:42 ` Balbir Singh
2008-06-30 19:52 ` Andrew Morton
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=20080606204005.GA4283@perlcode.org \
--to=scott@bluehost.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@bluehost.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.