Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
10-26-2003, 05:44 PM
|
#1
|
|
LQ Newbie
Registered: Oct 2003
Posts: 7
Rep:
|
XSession-errors file eats my hard drive
.xsession-errors file in my home directory sometimes grows up to severeal hundred MB, although I don't experience any strange X server behaviour. It's a fresh SuSE 9 install. Can I disable writing to this file?
|
|
|
|
10-26-2003, 06:01 PM
|
#2
|
|
Member
Registered: Oct 2003
Location: Rochester, New York (USA)
Distribution: Debian
Posts: 119
Rep:
|
Some applicaion must be generating a lot of errors. Can you tell of some message or set of messages is being repeated in the file ?
Tim
|
|
|
|
10-27-2003, 08:26 AM
|
#3
|
|
LQ Newbie
Registered: Oct 2003
Posts: 7
Original Poster
Rep:
|
I've found out that most of the errors are generated by playing divx movies:
fifo_audio_out: blocked for more than 20 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 47 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 47 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 47 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 46 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 47 ms,
fifo_audio_out: 1152 sample(s) discarded.
fifo_audio_out: blocked for more than 47 ms,
(...)
and this goes on and on for hundreds of MB (if I watch the whole movie).
|
|
|
|
10-27-2003, 10:18 AM
|
#4
|
|
Member
Registered: Oct 2003
Location: Rochester, New York (USA)
Distribution: Debian
Posts: 119
Rep:
|
It looks to me like an application may have been configured with debugging turned on.
Do you know what application is generating these messages ? Is it something you compiled yourself or was it part of the distribution.
If you're using KDE you might be able to modify the applink icon or menu entry so that the app is run with standard error directed to /dev/null. The line would look like this :
program_name &> /dev/null
Tim
|
|
|
|
10-27-2003, 11:20 AM
|
#5
|
|
LQ Newbie
Registered: Oct 2003
Posts: 7
Original Poster
Rep:
|
Thanks for your help Tim.
Those messages are generated by Kaffeine and Noatun - default media players on SuSE, however that doesn't happen with Totem, so I'll stick with it if I can't manage to fix this..
For some reason I can't play the movie if I start the player with that option. Is there a way to make all applications send standard error messages to /dev/null ?
|
|
|
|
10-27-2003, 03:31 PM
|
#6
|
|
Member
Registered: Oct 2003
Location: Rochester, New York (USA)
Distribution: Debian
Posts: 119
Rep:
|
No I don't think so. I don't know why the program won't run with stdout and stderr thrown away. You might also try the following :
program_name 2> /dev/null (only discards stderr, not stdout)
program_name 2> /dev/null &
Tim
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 12:48 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|