[arch-general] Slim login manager is logging everything
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues. I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim? thanks, Ananda
On Sat, 19 Jun 2010 21:01:53 +0200, Ananda Samaddar <ananda@samaddar.co.uk> wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim?
thanks,
Ananda
I'm using xdm with a modified xdm-archlinux (blackified) theme since a week or so. It is simple and it just works! I've used Slim before and after that I didn't use anything, just autologon, but that isn't really safe for a laptop. I'm not sure about the log files, never took a look at it. -- To read: http://en.wikipedia.org/wiki/Posting_style#Bottom-posting
On Sat, Jun 19, 2010 at 3:01 PM, Ananda Samaddar <ananda@samaddar.co.uk> wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim?
thanks,
Ananda
You can try qingy.
On Sat, 19 Jun 2010 17:09:10 -0400 Eric Bélanger <snowmaniscool@gmail.com> wrote:
You can try qingy.
I'd prefer something X11 based if possible. Has anyone tried lxdm? It looks good and only depends on Gtk. Seeing as XFCE depends on Gtk that's not an issue for me. Ananda
Excerpts from Ananda Samaddar's message of 2010-06-19 23:18:55 +0200:
On Sat, 19 Jun 2010 17:09:10 -0400 Eric Bélanger <snowmaniscool@gmail.com> wrote:
You can try qingy.
I'd prefer something X11 based if possible. Has anyone tried lxdm? It looks good and only depends on Gtk. Seeing as XFCE depends on Gtk that's not an issue for me.
Ananda
Do you need a login manager? I feel very comfortable with just 'startx'. -- Regards, Philipp -- "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
On Saturday 19 of June 2010 21:01:53 Ananda Samaddar wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim?
thanks,
Ananda I'm not sure I get you right, but 8gb is crazy.. how about use somehow logrotate/cron to delete the log file? --
Marek Otahal :o)
On 20/06/10 04:24, Marek Otahal wrote:
I'm not sure I get you right, but 8gb is crazy.. how about use somehow logrotate/cron to delete the log file?
I run slim on an eee and have /var/log on a 5mb tmpfs, so I ran into this problem quickly. I run logrotate every hour (/etc/cron.hourly/) and limit log files to 100k. For example, /etc/logrotate.d/slim: /var/log/slim.log { compress rotate 4 size 100k notifempty missingok copytruncate noolddir } That's extreme of course, and I might as well just send it to /dev/null instead, but it works. Daniel
Le 19/06/2010 21:01, Ananda Samaddar a écrit :
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
Same problem here. Deactivated logs was the only solution I found for the moment....
I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim?
thanks,
Ananda
Storm
On 06/19/2010 08:01 PM, Ananda Samaddar wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
I'm an XFCE user so I'd like to avoid kdm and gdm. Are are there any other alternative X11 login apps other than xdm that don't depend on GNOME or KDE if I can't fix my issue with Slim?
thanks,
Ananda
I'm not using a login manager, I do an auto-login after I input my username and password from tty1. I do that by checking from which tty I am starting and issuing a startx if it is tty1 (not my idea, I've seen that in the forums). However I've done a few modifications, the one that might be able to help you is that I do a 'startx > /dev/null'. This is really needed, otherwise some programs will mysteriously fail to work. The thing here is that you should try to find the place where slim writes to the log and redirect it to /dev/null instead of the log file and your problem should be solved. Maybe easier said than done but I guess you welcome any idea :p -- Mauro Santos
On 20/06/10 05:01, Ananda Samaddar wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
How old is the log file. I use slim and it is getting rotated frequently enough that it is only ~200MB at the worst. Allan
On Sat, Jun 19, 2010 at 9:51 PM, Allan McRae <allan@archlinux.org> wrote:
On 20/06/10 05:01, Ananda Samaddar wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
How old is the log file. I use slim and it is getting rotated frequently enough that it is only ~200MB at the worst.
Allan
The problem is that SLIM sets stdout and stderr to the log file and then everything started afterwards seems to inherit that unless it has a console or sets them itself. Because of that I once filled my hard drive testing a program that got stuck in an infinite loop.
On Sat, 19 Jun 2010 21:54:47 -0400 Shacristo <shacristo@gmail.com> wrote:
On Sat, Jun 19, 2010 at 9:51 PM, Allan McRae <allan@archlinux.org> wrote:
On 20/06/10 05:01, Ananda Samaddar wrote:
I'm using Slim as my login manager and it's logging absolutely everything. Things like gstreamer and alsa errors. This is making the log file huge, of the order of 8 gb when compressed. Can anyone think of a solution? I could always use the hack of putting the logfile in /tmp but I don't want to do that. /var is not on a separate partition and I'm not prepared to re-partition my system. Obviously with such large logfiles I'm getting performance issues.
How old is the log file. I use slim and it is getting rotated frequently enough that it is only ~200MB at the worst.
Allan
The problem is that SLIM sets stdout and stderr to the log file and then everything started afterwards seems to inherit that unless it has a console or sets them itself. Because of that I once filled my hard drive testing a program that got stuck in an infinite loop.
That makes sense now, one of the log files gzipped by logrotate was 8gb! Would setting the log file to /dev/null be ok as a workaround for the mean time, it won't break anything will it? When I get a chance though I'm going to have a look at lxdm. Ananda
participants (10)
-
Allan McRae
-
Ananda Samaddar
-
ChemicalStorm
-
Daniel Bumke
-
Eric Bélanger
-
Jeroen Op 't Eynde
-
Marek Otahal
-
Mauro Santos
-
Philipp Überbacher
-
Shacristo