At 1:29 PM -0700 9/9/02, Pete Stephenson imposed structure on a stream of electrons, yielding: >Ok, here's my setup -- I have SIMS (1.8b9, I think...something like >that.) running on an old 6115CD with Mac OS 9 on it. It's running >beautifully, with the exception of disk space (it's only got 350Mb >disk, and with the OS, it leaves about 120Mb left). > >Here's my problem -- my main computer is a PowerMac 6500/250 running >OS 9.1. It's been ok, but a little slow (even with a 500Mhz G3 >upgrade, I blame a slow system bus) as of late. Actually, today, it >looks like it went down for the count. I'm thinking of scrapping it >and getting a PowerMac G4 running OS X. > >Right now, I have a G4 TiBook running 10.2, with my main browser as >OmniWeb. I used to use CommuniGator on my 6500 to monitor the >mailserver in realtime (I loved the SMTP status window, and would >always keep logs open). I can deal with managing everything by HTTP, >but I can't look at the logs with OmniWeb (I know the logs are in >realtime, but OmniWeb for some reason will only display things up >until about 20 minutes before realtime, and doesn't automatically >continue to load, as Netscape does.)
Arguably the OmniWeb (and iCab) behavior is correct, since the HTML container with the log text is unterminated and the session is unclosed. >Is there any way to carbonize Communigator (that'd be the best >option for me), or somehow coordinate with the OmniWeb folks to see >if there's any way to make it all work...or is there some sort of >alternate solution that I'm missing? Sick alternative solution: put your logs on a directory mounted from the 10.2 machine and open a terminal window with a shell in that directory. Run this: tail -f 2002-09-10 |tr "\r" "\n" This will display the entire log file, and leave you with a current display that will update as the file is written to. The 'tail -f <filename>' part is a command to show the last lines of the file and keep watching for more new lines being added. The 'tr' command and the display of the entire file instead of just the last few lines are due to the fact that Unix wants linefeeds (\n) for line breaks while the classic MacOS uses carriage returns (\r) so that file is really just one big long line as far as that tail -f is concerned. Another twisted terminal alternative could probably rigged up with curl and lynx, but I haven't tried that. If you want to get really fancy you can do this, have a symlink maintained by cron to always point to the current file and use -F instead of -f, and even grep out things you really care (or don't care) about. -- Bill Cole [EMAIL PROTECTED] ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
