| Author |
Message |
|
graysky
|
 Posted: Thu Aug 21, 2008 2:30 pm |
|
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
My ~/.xsession-errors log is huge (over 40 megs) and contains entries like this:
Code: Xsession: X session started for mythtv at Wed Aug 20 16:28:42 EDT 2008
/home/mythtv/.fluxbox/startup: line 12: /usr/bin/bsetroot: No such file or directory
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.modKey
Setting default value
Failed to read: session.screen0.reversewheeling
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.userFollowModel
Setting default value
Failed to read: session.screen0.allowRemoteActions
Setting default value
Failed to read: session.screen0.tabs.maxOver
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting default value
BScreen::BScreen: managing screen 0 using visual 0x21, depth 24
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.modKey
Setting default value
Failed to read: session.screen0.reversewheeling
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.userFollowModel
Setting default value
Failed to read: session.screen0.allowRemoteActions
Setting default value
Failed to read: session.screen0.tabs.maxOver
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting default value
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.modKey
Setting default value
Failed to read: session.screen0.reversewheeling
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.userFollowModel
Setting default value
Failed to read: session.screen0.allowRemoteActions
Are these normal?
Can someone else have a look at your .xsession-errors file and see:
1) How large it is ($ ls -lha /home/mythtv | grep .xsession
2) Are the contents of your file similar to mine?
Thanks!
_________________
Retired KM user (R4 - R6.04); friend to LH users.
|
|
| Top |
|
 |
|
manicmike
|
Posted: Thu Aug 21, 2008 4:00 pm |
|
|
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location:
Melbourne, Australia
|
|
Hi Graysky,
The problem is that mythfrontend logs everything there if it can't write to /var/log/mythtv/mythfrontend. Now, when you installed KM, it probably started mythfrontend as root, and created the file as root, thus preventing any subsequent logging to that file. Have a look. If it's owned by root, change it to mythtv and re-start the frontend.
The correct log file is able to be rotated easily using logrotate.
Alternatively, you could write a cron job to check the size each day and truncate it.
Regards
Mike
P.S. 40MB isn't huge: I've seen this file at 2.5GB!
_________________
*********************
LinHES 7.4
Australian Dragon
*********************
|
|
| Top |
|
|
|
graysky
|
Posted: Thu Aug 21, 2008 4:50 pm |
|
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
Thanks for the reply, Mike. I checked, and the log files have the correct permissions:
Code: -rw-r--r-- 1 mythtv mythtv 188K Jul 14 19:06 KnoppMyth-run.log
-rw-r--r-- 1 mythtv mythtv 409K Aug 21 18:50 mythbackend.log
-rw-r--r-- 1 mythtv mythtv 935K Aug 9 06:26 mythbackend.log.1
-rw-r--r-- 1 mythtv mythtv 15K Aug 16 04:54 mythfrontend.log
-rw-r--r-- 1 mythtv mythtv 60K Aug 16 04:54 mythwelcome.log
_________________
Retired KM user (R4 - R6.04); friend to LH users.
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Aug 21, 2008 7:23 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
You can always truncate it and restart the FE:
Code: > /home/mythtv/.xsession-errors
pkill xinit
Mine is only about 70k at the moment, but I've been rebooting about once a week to keep the Nvidia drivers memory leak from sending my system off to swap thrashing land.
|
|
| Top |
|
|
|
jmckeown2
|
Posted: Thu Aug 21, 2008 8:06 pm |
|
|
Joined: Sat Sep 02, 2006 9:17 am
Posts: 359
|
manicmike wrote: The problem is that mythfrontend logs everything there if it can't write to /var/log/mythtv/mythfrontend. Now, when you installed KM, it probably started mythfrontend as root, and created the file as root, thus preventing any subsequent logging to that file. Have a look. If it's owned by root, change it to mythtv and re-start the frontend.
Thanks! mine was 26MB, and I would have never thought to look.
|
|
| Top |
|
|
|
cahlfors
|
Posted: Fri Oct 10, 2008 9:40 am |
|
|
Joined: Tue Jan 23, 2007 1:38 pm
Posts: 251
Location:
Sweden
|
|
Ah-ha!
Hm. My permissions are right, but mythfrontend still logs to .xsession-errors on all my FE:s. How do I change that?
Thanks
/Chris
_________________
LinHES R8.6.1
BE: AMD64X4, 4GB, Hauppauge usb tuners
FE1: Gigabyte F2A85X-UP4, nVidia GT640
FE2: Gigabyte GA-MA69GM-S2H, AthlonX2 4850E 2.5 GHz, 1GB, ASUS GEFORCE 7200GS 256MB
FE3: Asus Eeebox410
|
|
| Top |
|
|
|
manicmike
|
Posted: Sun Oct 12, 2008 9:03 pm |
|
|
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location:
Melbourne, Australia
|
cahlfors wrote: Ah-ha!
Hm. My permissions are right, but mythfrontend still logs to .xsession-errors on all my FE:s. How do I change that?
Thanks
/Chris
How about this:
1. su -c "mv .xsession-errors /var/log/mythtv/" <enter root passwd when prompted>
2. ln -s /var/log/mythtv/.xsession-errors .xsession-errors
This will move it from the root file system to the /myth file system. If it gets big, it won't kill the system. This is just a quick fix to stop your root fs from filling.
Mike
_________________
*********************
LinHES 7.4
Australian Dragon
*********************
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
