ports/121360: Change default of ~/.xsession-errors to off and document it.

[Mel]

>Number:         121360
>Category:       ports
>Synopsis:       Change default of ~/.xsession-errors to off and document it.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 04 16:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Charlie &
>Release:        FreeBSD 7.0-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD smoochies.rachie.is-a-geek.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Fri Feb 22 03:36:50 AKST 2008 root at smoochies.rachie.is-a-geek.net:/usr/obj/usr/src/sys/GENERIC-ULE i386


	
>Description:
# man -k xsession-errors
xsession-errors: nothing appropriate

This file gets created on a default Xorg installation, since 7.x I believe.
This file just grew to 1G, in a user's home directory, cause amor
(x11-clocks/kdetoys3) doesn't handle invalid window id's very well and loops
like a maniac.
This also gets recorded into .xsession-errors each and every time, adding to
the problem and frankly, having it in there a million times helps no one.
Not sure why X isn't capable of using standard syslog semantics, but that's
beside the problem.
It would be very nice if this is default off and documented somewhere within
the man(1) domain how to turn it off.
>How-To-Repeat:
start x and watch xsession-errors grow. Write a prog that discards an invalid
window id and just requests it again till it gets it. See if you have disk-
space available after a few hours.
>Fix:
None known.
	


>Release-Note:
>Audit-Trail:
>Unformatted: