On Fri, 22 Dec 2000 20:17:28 GMT,
[EMAIL PROTECTED] (Marc Haber) wrote:
I am maintainer for run and console-log, and waiting for NM to
complete. Unfortunately, run has a nasty bug that causes console-log
to hang which in turn may prevent a clean shutdown. I don't have the
expertise to fix this one
On Tue, 26 Dec 2000 07:28:59 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
It sounds pretty easy to implement; just stat() and compare the inode number.
That won't catch a file being copied and truncated since the inode
stays the same.
Greetings
Marc
--
--
On Wed, Dec 27, 2000 at 11:26:25AM +, Marc Haber wrote:
On Tue, 26 Dec 2000 07:28:59 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
It sounds pretty easy to implement; just stat() and compare the inode number.
That won't catch a file being copied and truncated since the inode
stays the
On Mon, 25 Dec 2000 08:36:34 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
Though maybe this program is forcing itself on the wrong interface to syslog.
Maybe it should really be reading from a fifo, a la /dev/xconsole, rather than
trying to read from files.
Having this, it would be impossible
On Tue, Dec 26, 2000 at 11:27:32AM +, Marc Haber wrote:
On Mon, 25 Dec 2000 08:36:34 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
Though maybe this program is forcing itself on the wrong interface to syslog.
Maybe it should really be reading from a fifo, a la /dev/xconsole, rather
On 00-12-25 Matt Zimmerman wrote:
On Mon, Dec 25, 2000 at 01:29:44PM +, Marc Haber wrote:
On Sat, 23 Dec 2000 15:41:54 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
However, I would say that if the program dies so frequently that it needs a
wrapper like this, it should probably be
On Tue, Dec 26, 2000 at 12:26:10PM +0100, Christian Kurz wrote:
On 00-12-25 Matt Zimmerman wrote:
It would be nice if less included a feature to close and reopen the current
file. Then this would not be necessary.
Well, this is a feature that tail on FreeBSD has. If you start it with
Today, Christian Kurz [EMAIL PROTECTED] wrote:
Well, this is a feature that tail on FreeBSD has. If you start it with
-F, it will tail you the current file like our tail -f. But if know the
logfile will be rotated, it will notice this and reopen the new current
one and tail this one. This is a
On Tue, Dec 26, 2000 at 12:26:10PM +0100, Christian Kurz wrote:
Well, this is a feature that tail on FreeBSD has. If you start it with
-F, it will tail you the current file like our tail -f. But if know the
logfile will be rotated, it will notice this and reopen the new current
one and tail
On Tue, Dec 26, 2000 at 01:38:03PM +0100, Andreas Fuchs wrote:
Today, Christian Kurz [EMAIL PROTECTED] wrote:
Well, this is a feature that tail on FreeBSD has. If you start it with
-F, it will tail you the current file like our tail -f. But if know the
logfile will be rotated, it will
On 00-12-26 Andreas Fuchs wrote:
Today, Christian Kurz [EMAIL PROTECTED] wrote:
Well, this is a feature that tail on FreeBSD has. If you start it with
-F, it will tail you the current file like our tail -f. But if know the
logfile will be rotated, it will notice this and reopen the new
On 00-12-26 Ethan Benson wrote:
On Tue, Dec 26, 2000 at 12:26:10PM +0100, Christian Kurz wrote:
Well, this is a feature that tail on FreeBSD has. If you start it with
-F, it will tail you the current file like our tail -f. But if know the
logfile will be rotated, it will notice this and
On 00-12-26 Matt Zimmerman wrote:
On Tue, Dec 26, 2000 at 12:26:10PM +0100, Christian Kurz wrote:
On 00-12-25 Matt Zimmerman wrote:
It would be nice if less included a feature to close and reopen the
current
file. Then this would not be necessary.
Well, this is a feature that
On Sat, 23 Dec 2000 15:41:54 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
On Sat, Dec 23, 2000 at 06:46:46PM +, Marc Haber wrote:
You'd have to have a ton of precautions. The task at hand seems
trivial, but it isn't :-(
init does a good job of this; if there were an easy, error-proof way
On Sat, 23 Dec 2000 15:41:54 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
However, I would say that if the program dies so frequently that it needs a
wrapper like this, it should probably be fixed.
console-log uses less syslog which dies every time the user types Q.
And it needs to die if the
On Mon, Dec 25, 2000 at 01:29:44PM +, Marc Haber wrote:
On Sat, 23 Dec 2000 15:41:54 -0500, Matt Zimmerman [EMAIL PROTECTED]
wrote:
However, I would say that if the program dies so frequently that it needs a
wrapper like this, it should probably be fixed.
console-log uses less syslog
On 2000-12-23, Matt Zimmerman [EMAIL PROTECTED] wrote:
Yes and no. It can daemonize a program, but will not restart it when it dies.
It sounds like what you want is a simple shell script that would be daemonized
by start-stop-daemon:
/usr/sbin/myprogram.wrapper:
However, I would say that
On Sun, Dec 24, 2000 at 11:04:10AM +0100, Andreas Fuchs wrote:
However, I would say that if the program dies so frequently that it needs a
wrapper like this, it should probably be fixed.
tail -f of a logfile into a secured less. To search and scroll
backwards, one must kill the tail,
Matt Zimmerman ([EMAIL PROTECTED]) said:
less has a mode to select() and watch the end of a file, invoked with
the 'F' command. I don't think that it's currently possible for less to
enter this mode with a command-line flag, but I've often wished that it did,
so maybe this feature should be
On 2000-12-22, Erik Steffl [EMAIL PROTECTED] wrote:
Marc Haber wrote:
Hi,
I am maintainer for run and console-log, and waiting for NM to
[...]
To keep console-log, I need a program that can daemonize a normal
program, i.e. put it in the background, maintain a pid file unter
/var/run and
On Sat, 23 Dec 2000 09:14:25 +0100, Andreas Fuchs [EMAIL PROTECTED] wrote:
start-stop-daemon won't work,
start-stop-daemon IIRC needs $program to background itself, and it
can't IIRC restart dying processes. run stays around to keep a watch
on its child.
I wonder if a sh script could do what
On Sat, Dec 23, 2000 at 06:46:46PM +, Marc Haber wrote:
On Sat, 23 Dec 2000 09:14:25 +0100, Andreas Fuchs [EMAIL PROTECTED] wrote:
start-stop-daemon won't work,
start-stop-daemon IIRC needs $program to background itself, and it
can't IIRC restart dying processes. run stays around to
Hi,
I am maintainer for run and console-log, and waiting for NM to
complete. Unfortunately, run has a nasty bug that causes console-log
to hang which in turn may prevent a clean shutdown. Upstream doesn't
maintain run any more (and I shouldn't have packaged it in the first
place), and isn't
Marc Haber wrote:
Hi,
I am maintainer for run and console-log, and waiting for NM to
complete. Unfortunately, run has a nasty bug that causes console-log
to hang which in turn may prevent a clean shutdown. Upstream doesn't
maintain run any more (and I shouldn't have packaged it in the
24 matches
Mail list logo
