Console Mac OS X.3 on G3's

2005-06-11 Thread Christian Kotz
Anyone know how I can stop console from generating randomly sized log's 
namely the log titled console.log that syphons off my Hard drives 
existing space when the computer is left on for over 24 hours non-stop? 
All other console logs remain around 4kb but this one seems to grow 
especially when the computer is on the internet. So far I can only 
recover the space by moving the log to the trash, restarting and 
emptying the trash after reboot. It's a little annoying especially 
during downloads. Any ideas appreciated :)


Regards Christian



Re: Console Mac OS X.3 on G3's

2005-06-11 Thread Rob Findlay
What size are we talking here? My computer is connected to the new via
airport 24/7 and my whole Library/log/console/ folder is about 60k with logs
going back to last month. Have you tried reading the logs to find out what
is generating all the data?


On 11/6/05 12:01 AM, Christian Kotz [EMAIL PROTECTED] wrote:

 Anyone know how I can stop console from generating randomly sized log's
 namely the log titled console.log that syphons off my Hard drives
 existing space when the computer is left on for over 24 hours non-stop?
 All other console logs remain around 4kb but this one seems to grow
 especially when the computer is on the internet. So far I can only
 recover the space by moving the log to the trash, restarting and
 emptying the trash after reboot. It's a little annoying especially
 during downloads. Any ideas appreciated :)
 
 Regards Christian
 
 
 -- The WA Macintosh User Group Mailing List --
 Archives - http://www.wamug.org.au/mailinglist/archives.shtml
 Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
 Unsubscribe - mailto:[EMAIL PROTECTED]
 
 WAMUG is powered by Stalker CommuniGatePro
 




Re: Console Mac OS X.3 on G3's

2005-06-11 Thread Christian Kotz
I'm talking a growth from 4KB to 2.5GB and 3GB. The thing is it's 
unrecognisable and caused console to crash when opening the massive 
log. I'm getting the same issue on 3 G3's that are connected to 
internet over Airport and when left on over night generate 3 gig of 
logging that syphons all hard drive space. Restart recovers say 300MB 
and deleting the log recovers all space.


Regards Christian
On 11/06/2005, at 12:14 AM, Rob Findlay wrote:


What size are we talking here? My computer is connected to the new via
airport 24/7 and my whole Library/log/console/ folder is about 60k 
with logs
going back to last month. Have you tried reading the logs to find out 
what

is generating all the data?


On 11/6/05 12:01 AM, Christian Kotz [EMAIL PROTECTED] wrote:

Anyone know how I can stop console from generating randomly sized 
log's

namely the log titled console.log that syphons off my Hard drives
existing space when the computer is left on for over 24 hours 
non-stop?

All other console logs remain around 4kb but this one seems to grow
especially when the computer is on the internet. So far I can only
recover the space by moving the log to the trash, restarting and
emptying the trash after reboot. It's a little annoying especially
during downloads. Any ideas appreciated :)

Regards Christian


-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]

WAMUG is powered by Stalker CommuniGatePro





-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]

WAMUG is powered by Stalker CommuniGatePro





Re: Console Mac OS X.3 on G3's

2005-06-11 Thread James Devenish
Hi,

In message [EMAIL PROTECTED]
on Sat, Jun 11, 2005 at 04:38:10PM +0800, Christian Kotz wrote:
 I'm talking a growth from 4KB to 2.5GB and 3GB. The thing is it's 
 unrecognisable and caused console to crash when opening the massive 
 log.

You'll have to find a way of reading console.log. One way is to go to
the Terminal (Applications  Utilities). There, you'll need to type:

tail /Library/Logs/Console/$USER/console.log

Hopefully, the cause of the problem will be apparent after that
(might not be, though).