| Summary: | accept FIFOs ("|<path>") as log destinations in /etc/syslog.conf | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | Christoph Schulz <develop> |
| Component: | Other | Assignee: | unassigned |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | 1.22.x | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: |
allows entries with a FIFO as log destination in /etc/syslog.conf
allows entries with a FIFO as log destination in /etc/syslog.conf allows entries with a FIFO as log destination in /etc/syslog.conf |
||
Created attachment 4586 [details]
allows entries with a FIFO as log destination in /etc/syslog.conf
now ignores SIGPIPE
Version set to busybox 1.22.1. Created attachment 5606 [details]
allows entries with a FIFO as log destination in /etc/syslog.conf
Submitted patch updated to busybox 1.22.1.
|
Created attachment 4556 [details] allows entries with a FIFO as log destination in /etc/syslog.conf Hello, sysklogd accepts something like "kern.info |/var/log/kernel-info", where /var/log/kernel-info is a pre-created FIFO. The syslogd man page says: This version of syslogd has support for logging output to named pipes (fifos). A fifo or named pipe can be used as a destination for log messages by prepending a pipy symbol (``|'') to the name of the file. This is handy for debugging. Note that the fifo must be created with the mkfifo command before syslogd is started. I attached a small patch (applies to busybox 1.20.2) which modifies syslogd.c to handle such targets, too. Regards, Christoph Schulz