Mailinglist Archive: opensuse (2348 mails)

< Previous Next >
Re: [opensuse] Xinetd -d writing to a file?

----- Original Message -----
From: "Kain, Becki (B.)" <bkain1@xxxxxxxx>
To: <opensuse@xxxxxxxxxxxx>
Sent: Tuesday, April 01, 2008 3:50 PM
Subject: RE: [opensuse] Xinetd -d writing to a file?

nope, it still writes to the screen. It did create the logfile, but
it's 0 length

You never heard of stderr vs stdout?

xinetd -d 2>&1 | tee /path/to/logfile

man bash
man tee


I have, actually, thanks and that doesn't work:

startproc -t 1 $XINETD_BIN -d 2>&1 | tee

In /etc/init.d/xinetd will create the log file, never write to it, and
continues to blast to the screen.

Thanks though, for the reminder of man



We didn't say startproc we said xinetd.

startproc could be (usually is) a shell function sourced from somewhere like
the ". /etc/rc.status" near the top of /etc/init.d/xinetd or in some parent
script that ran /etc/init.d/xinetd or any earlier ancestor back to init.
Or it may be a script or a binary. In any case it may have it's own quirks
which would hopefully be explained in "man startproc" or if that doesn't exist,
maybe "apropos startproc" can find the man page that does have info. (ie: maybe
startproc is part of some rc package and it's behaviour is described in
something like "man init" or "man sysvinit"
No binary or script _has_ to output things to any particular tty or file
descriptor. stdout/stderr going to the current tty or the current pipeline is
merely a standard convention. Not a law of nature.

As it happens, in this case, "which startproc" returns "/sbin/startproc" which
is a binary and "man startproc" does exist and is reasonably enlightening.
Perhaps the -l option.

There are other possible gotchas but lets start with that.

Brian K. White brian@xxxxxxxxx
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >