Re: log-reader
tail -f yourLogFileHere ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 that, let me say that no ill-will should be read into my msg because it certainly wasn't written with any, and I didn't mean to imply that you're a Luser. I was just amused at how many of us piled on to answer that little query... . ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Subject: RE: log-reader
-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 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 that, let me say that no ill-will should be read into my msg because it certainly wasn't written with any, and I didn't mean to imply that you're a Luser. I was just amused at how many of us piled on to answer that little query... No, none was taken! I assure you. Hence the smiley, which was consciously placed. No implication was assumed, either, it was just self-beratement. Erik ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 changing Tx/Rx counts associated w/your Enets. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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). It is a very, simple, straightforward way to do it. 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. Be that as it may, it then becomes an interesting problem of what to do about the information as it rolls in. In my case, I do a 'tail -f /var/log/messages' as part of my ppp startup, and I can monitor real time any attempts to hit my system. But, realistically, that particular window is buried below (er, behind) my Netscape Navigator browser window, my Netscape e-mail window, and a couple of others, sometimes for hours, so I frequently don't notice when someone overseas decides to telnet or ftp my dial-up node. So, I'd love to have an audible beep and/or (*gasp*) a pop-up window telling me when I'm being, er, groped over the network. Any ideas? Thanks, Bayard ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 told that a certain large, well-known customer had a bunch of PDP-11/70's for some critical functions. The PDP-11 architecture had a very nice (IMNSHO) interrupt architecture, so that various events could be properly dispatched to their handler routines. There was even one for when the interrupt stacks themselves were corrupted. (Anyone remember the yellow-zone/red-zone stuff?). Well, this customer, well-known for its technology and its geek humor, set up their systems so that a trap to the 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 the system died. Thanks, Bayard ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: log-reader
On Thu, 21 Nov 2002, at 9:59am, [EMAIL PROTECTED] wrote: I seem to recall that there is a way to interactively read logfiles (as they are being generated) from the command line, but I completely forget what utility that is. A quick reminder, anyone? tail -f filename -- Ben Scott [EMAIL PROTECTED] | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: log-reader
tail -f /var/log/whatever. C-Ya, Kenny On Thu, 2002-11-21 at 09:59, Price, Erik wrote: Folks, I seem to recall that there is a way to interactively read logfiles (as they are being generated) from the command line, but I completely forget what utility that is. A quick reminder, anyone? (Right now I'm just lessing the files after the expected error is generated.) (on Gentoo Linux) Erik ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss -- Tact is just *not* saying true stuff -- Cordelia Chase Kenneth E. Lussier Sr. Systems Administrator Zuken, USA PGP KeyID CB254DD0 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xCB254DD0 ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: log-reader
Try this: tail -f someapp.log -Original Message- From: Price, Erik [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: log-reader Folks, I seem to recall that there is a way to interactively read logfiles (as they are being generated) from the command line, but I completely forget what utility that is. A quick reminder, anyone? (Right now I'm just lessing the files after the expected error is generated.) (on Gentoo Linux) Erik ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 the system died. I used the sound of breaking glass for a crash but this is much cooler. Tom goes looking for a human death scream sound -- --- Tom Buskey ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 user was already an Emacs user, and they wanted to do this under Emacs, they could use live-find-file. The Emacs process that I'm typing this in has been up since the last time my computer experienced a power failure. Most Emacs users start up Emacs and leave it up for the entire session, however long that might be. So I disagree with your judgement of unworthy. --kevin -- Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA) cetaceannetworks.com!kclark (GnuPG ID: B280F24E) alumni.unh.edu!kdc ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 clearly see that there's no cost associated with using it to check the logs. Conversely, starting up a separate invocation of emacs just to watch the logs seemed to me to be a bit expensive. 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? ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Subject: RE: log-reader
-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 experienced a power failure. Most Emacs users start up Emacs and leave it up for the entire session, however long that might be. Lo, and it is indeed even inscribed unto the Emacs tutorial that said behavior is recommendation-worthy. That's actually the first time I really used Ctrl-z, was when learning Emacs ... I knew about the command but felt like it was bad form to suspend processes. When I saw it recommended in yon Emacs tutorial, I asked about it and found that it's not like putting a video tape on pause ... (this was years ago, I was much younger and even more naive, really) Erik ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Subject: RE: log-reader
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 you invoke gnuserv-start when Emacs is fired up, you can then do things like set your EDITOR/VISUAL variables to 'gnuclient' and anything that invokes your editor with send that to the gnuserv process. You can also, from the cmd line use 'gnuclient foo.txt' which does the same thing. -- Seeya, Paul -- It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
