d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Explain a little more about the piping feature.

Browse Source 
PR:		4122
This commit is contained in:
joerg 1997-09-14 06:55:15 +00:00
parent 5b4e745b7a
commit 4d85218738
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
usr.sbin/syslogd/syslog.conf.5
View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)syslog.conf.5 8.1 (Berkeley) 6/9/93
.\" $Id$
.\" $Id: syslog.conf.5,v 1.6 1997/04/29 09:09:40 jmg Exp $
.\"
.Dd June 9, 1993
.Dt SYSLOG.CONF 5
@ -235,10 +235,14 @@ Upon receipt of a
will close the pipe to the process. If the process didn't exit
voluntarily, it will be sent a
.Dv SIGTERM
signal after a grace period of up to 40 seconds.
signal after a grace period of up to 60 seconds.
.Pp
The command will only be started once data arrives that should be piped
to it. If it exited later, it will be restarted as necessary.
to it. If it exited later, it will be restarted as necessary. So if it
is desired that the subprocess should get exactly one line of input only
(which can be very resource-consuming if there are a lot of messages
flowing quickly), this can be achieved by exiting after just one line of
input. If necessary, a script wrapper can be written to this effect.
.Pp
Unless the command is a full pipeline, it's probably useful to
start the command with