More MacOSX Trouble
01-Jan-2008 12:20 Filed in: REBOL
General | MacOSX
Happy New Year!
And now for something more serious: As it turned out, turning off the spinning terminal indicator is not only important in the console. It's also important, if you are launching your process as a service using Launchd, the standard way to handle background services under MacOSX, because Launchd logs all output from a process in /var/log/system.log.
I noticed that Console.app would hang immediately on start up. That usually means that system.log is being updated intensively, and CPU usage was higher than normal.
So I resorted to:
Imagine my horror seeing this scrolling very rapidly up the terminal:
So you see how important it is to quiet it down!
But what if you don't have the option of quieting the script down from inside the script itself?
You can do this during call, or if you are starting REBOL from the command line directly with a script, like so:
I hope you'll find this tip useful.
And now for something more serious: As it turned out, turning off the spinning terminal indicator is not only important in the console. It's also important, if you are launching your process as a service using Launchd, the standard way to handle background services under MacOSX, because Launchd logs all output from a process in /var/log/system.log.
I noticed that Console.app would hang immediately on start up. That usually means that system.log is being updated intensively, and CPU usage was higher than normal.
So I resorted to:
tail -f /var/log/system.log
Imagine my horror seeing this scrolling very rapidly up the terminal:
Jan 1 11:01:43 Macintosh com.rebol.cheyenne[60072]: /
Jan 1 11:01:43: --- last message repeated 1 time ---
Jan 1 11:01:43 Macintosh com.rebol.cheyenne[60072]: -
Jan 1 11:01:43: --- last message repeated 1 time ---
Jan 1 11:01:43 Macintosh com.rebol.cheyenne[60072]: \
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: -
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: \
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: -
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |
Jan 1 11:01:44: --- last message repeated 1 time ---
Jan 1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan 1 11:01:45: --- last message repeated 1 time ---
Jan 1 11:01:45 Macintosh com.rebol.cheyenne[60072]: -
Jan 1 11:01:45: --- last message repeated 1 time ---
Jan 1 11:01:45 Macintosh com.rebol.cheyenne[60072]: \
Jan 1 11:01:45: --- last message repeated 1 time ---
Jan 1 11:01:45 Macintosh com.rebol.cheyenne[60072]: |
Jan 1 11:01:45: --- last message repeated 1 time ---
Jan 1 11:01:45 Macintosh com.rebol.cheyenne[60072]: /
So you see how important it is to quiet it down!
But what if you don't have the option of quieting the script down from inside the script itself?
You can do this during call, or if you are starting REBOL from the command line directly with a script, like so:
$ rebol -q <script-name>
I hope you'll find this tip useful.
|