I wrote:
prettyMuchEverybody wrote:
tail -f logfile
Sheesh. I hereby certify us all as Linux Professionals.
Erik wrote:
Fine by me. It makes me look less stupid for not knowing. ;)
That would at least make me a Linux User, as opposed to a Linux Luser.
Since I'm not sure how you took
-Original Message-
From: Michael O'Donnell [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 10:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Subject: RE: log-reader
I wrote:
prettyMuchEverybody wrote:
tail -f logfile
Sheesh. I hereby certify us all
FYI, another way to monitor changing events
is via the watch command, though it's used
in slightly different circumstances than the
OP asked about; it's prepared to repeatedly
execute some command and keep the screen
updated with the results. Example:
watch ifconfig
...will show the
As an alternate solution, if the original poster is an Emacs user, he
could have used live-find-file.
--kevin
--
Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA)
cetaceannetworks.com!kclark (GnuPG ID: B280F24E)
alumni.unh.edu!kdc
___
I was amused by this whole discussion, since the trick of
using 'tail -f filename' is fairly universal amongst the
various UNIX implementations. I used it for years on Tru64
UNIX and its antecedants while monitoring my testing (I did
TruCluster software QC for several years before my retirement).
OK great -
Both Tom and Ben Boulanger nominated 'swatch', which goes to
show that you can teach an old dog like me new tricks.
The capability of triggering a sound event is fairly routine
nowadays, both under Linux as well as under certain MS products.
Back when I started with DEC in '78, I was
Bayard R. Coolidge said:
system crash vector would close a relay contact and set off
an audible alarm. In their case, it was a tape recording of
a human death scream. Rather unnerving for service personnel
on their first service calls to this particular facility,
but at least everyone knew when
Bayard R. Coolidge [EMAIL PROTECTED] writes:
I submit
that firing up an entire editor (e.g. emacs, as suggested by
Kevin Clark) is an unworthy consumption of valuable system
resources, however fun it might be.
I never suggested firing up an editor to do this. I merely suggested
that if the
Thanks for the clarification, as I generally invoke an editor
ad hoc for editing specific documents, and then dissolve it when
I'm done. If you (and other emacs users) fire it up as part of
your initial window invocations and leave it up during your entire
working session then, yes, I can
-Original Message-
From: Kevin D. Clark [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 1:58 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Subject: RE: log-reader
The Emacs process that I'm typing this in has been up since the last
time my computer
In a message dated: Thu, 21 Nov 2002 14:22:49 EST
Michael O'Donnell said:
Doesn't Emacs have a client-server mode (or version)
wherein one heavyweight Emacs process remains
resident in memory and then a bunch of lightweight
Emacs processes can connect to it?
Yes, gnuserver and gnuclient. If
11 matches
Mail list logo
