[Herman Robak] > Could ulimit and UL_SETFSIZE be used as a workaround? Not as far as I know.
> Since .xsession-errors is written to by the X server (I guess), this > might make the X server unhappy, or even crash, once the set limit > is reached. .xsession-errors is not written by the X server. It writes to /var/log/kdm.log. .xsession-errors is used by all the X clients. > And that would repeat itself pretty quick unless something else > wipes .xsession-errors out. A size test on .xsession-errors during > login, perhaps? Trunkation if it is to large at login might help in some settings, but not with programs producing a lot of such messages during one login. But perhaps we should try first with a 1 MB size limit and trunkate during login if it is above that, and see if it solve most of the problems. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
