You are not logged in.

#1 2011-07-18 16:22:50

nikolardo
Member
From: Canterbury, NH
Registered: 2011-04-16
Posts: 36
Website

slim.log is 6.9 GB

My root partition is being eaten up by slim.log.  It was originally a 7.5G partition, I think, and I recently expanded it to about 15G, and in the one day following (I think only two boots since doing this) I'm down to 1.5G free.

This is mostly due to my /var/log/slim.log file being 6.9 GB.

Why is that, and what can I do about it?

Offline

#2 2011-07-18 16:26:15

litemotiv
Forum Fellow
Registered: 2008-08-01
Posts: 5,026

Re: slim.log is 6.9 GB

So what is it logging? wink

Try:

$ tail -n 50 /var/log/slim.log

ᶘ ᵒᴥᵒᶅ

Offline

#3 2011-07-18 16:29:48

nikolardo
Member
From: Canterbury, NH
Registered: 2011-04-16
Posts: 36
Website

Re: slim.log is 6.9 GB

The output of "tail -n 50 /var/log/slim.log" is a bunch of firefox warnings (e.g. (firefox-bin:1109): GLib-GObject-WARNING **: g_object_get_property: object class `GtkToggleButton' has no property named `has-frame') and a lot of
start typing
stop typing
start typing
stop typing

Offline

#4 2011-07-18 16:43:34

toofishes
Developer
From: Chicago, IL
Registered: 2006-06-06
Posts: 602
Website

Re: slim.log is 6.9 GB

I thought this bug was fixed a while back; look around our bug reports or on the forums for some past talk. Your best bet immediately is to truncate it to size 0, but that won't fix the root cause. `sudo truncate --size=0 /var/log/slim.log`.

Offline

#5 2011-07-18 17:11:25

harryNID
Member
From: P3X-1971
Registered: 2009-06-12
Posts: 117

Re: slim.log is 6.9 GB

Obviously,  you are having a bug issue there and you'll want to try and find a fix for that but in the meantime you have a few options open to you until you find the culprit. First you could create a cron job to rotate it (perhaps daily or even hourly I would think?). If Firefox seems alright (functionally that is) you could also redirect Firefox's errors to /dev/null. That's not really a fix but you could keep your slim.log active without it filling up with all of Firefox's errors messages. Again, that is a temporary fix only. Barring that and if you don't use it you could do what I do and that is disable slim.log altogether. You do that by setting the "logfile" option in etc/slim/conf to /dev/null.

Edit: A long shot here but if you are using a custom theme try switching back to the default and see if you still get the error messages.

Last edited by harryNID (2011-07-18 17:44:08)


In solving a problem of this sort, the grand thing is to be able to reason backward. That is a very useful accomplishment, and a very easy one, but people do not practice it much. In the everyday affairs of life it is more useful to reason forward, and so the other comes to be neglected. There are fifty who can reason synthetically for one who can reason analytically.  --Sherlock Holmes

Offline

#6 2011-07-19 12:35:29

nikolardo
Member
From: Canterbury, NH
Registered: 2011-04-16
Posts: 36
Website

Re: slim.log is 6.9 GB

Thanks toolfishes and harryNID, I've implemented both the fixes (truncated it, then set it to write to /dev/null).  Now I have my root partition back!

Offline

Board footer

Powered by FluxBB