Printable View
my friend manages a server that runs debian and he asked me if i had ever heard of xsession.error logs being 17 gigz and i told him that i didnt. its brought the server down several times already, and i would be surprised if he hasnt tried the latest patches. does this sound like a bug or foul play, and how can he fix it?
Having X on a server is not good idea in the first place. Maybe he should like read what the errors are and correct them??? (no one is going to be able to tell you much of anything without specifics)
x isnt on the server (i now know) its on the workstations which is red hat 9. (the server is debian) and they have had two users' xsession.error logs inflate as big as possible and take up all disk space on the server makin it impossible for anyone to log in and save stuff. does that help at all? sorry if its confusing. im not all that great with nix.
Color me silly here ...but heQuote:
x isnt on the server
Am I missing something?Quote:
had two users' xsession.error logs inflate as big as possible and take up all disk space on the server
Might be better to provide more specifics as lumpyporridge suggested. Things like what type of server ( mail, samba, proxy, etc. ), excerpts from the error logs, what type of computers are accessing the server.