.serverauth.6297

ekdya · 05-06-2006, 09:34 PM

Hi

what is all those files in my $ ls -al

thanks

-rw------- 1 fred fred 153 2006-05-01 11:18 .serverauth.6297
-rw------- 1 fred fred 153 2006-05-03 15:24 .serverauth.6348
-rw------- 1 fred fred 153 2006-05-01 12:07 .serverauth.6381
-rw------- 1 fred fred 153 2006-04-30 19:23 .serverauth.6432
-rw------- 1 fred fred 153 2006-05-04 13:55 .serverauth.6439
-rw------- 1 fred fred 153 2006-05-04 19:35 .serverauth.6478
-rw------- 1 fred fred 51 2006-04-29 06:13 .serverauth.6490
-rw------- 1 fred fred 153 2006-04-30 06:43 .serverauth.6494
-rw------- 1 fred fred 153 2006-05-03 15:38 .serverauth.6497
-rw------- 1 fred fred 153 2006-05-05 14:08 .serverauth.6498
-rw------- 1 fred fred 153 2006-05-01 11:35 .serverauth.6500
-rw------- 1 fred fred 153 2006-05-02 14:52 .serverauth.6501
-rw------- 1 fred fred 153 2006-05-06 15:51 .serverauth.6503
-rw------- 1 fred fred 153 2006-05-01 13:06 .serverauth.6505
-rw------- 1 fred fred 153 2006-05-01 12:44 .serverauth.6553
-rw------- 1 fred fred 153 2006-05-03 22:04 .serverauth.6660

Randux · 05-07-2006, 01:44 PM

You can delete all that stuff. Each time you start an X windows session, that file gets created. I don't know why they're not being deleted; usually when the new one gets created the old one (if any) gets deleted. Or you could write a bash script to execute on shutdown or login to blast any old files.

Kovacs · 05-16-2006, 04:25 AM

Check out this page for details:
http://www.shallowsky.com/blog/index...erverauth.html

Basically the fix is to edit your /usr/bin/startx file (or whereever startx is located for your distro, /usr/X11R6/bin/startx for my Slackware 11 box), and change the line:

Code:

xserverauthfile=$HOME/.serverauth.$$

to:

Code:

xserverauthfile=$XAUTHORITY

You can then delete your .serverauth.???? files and from now on the X authority will be written to ~/.Xauthority, no more files cluttering up your home directory.

Dead Parrot · 05-16-2006, 04:52 AM

Good advice, Kovacs. But if you edit startx, then you'll have to do that again every time after you've upgraded Xserver.

It's better to create a file named .xserverrc into your home directory and add the xserverauthfile line there, like this:

Code:

#!/bin/sh
xserverauthfile=$XAUTHORITY

Then make .xserverrc executable (chmod +x .xserverrc).

ekdya · 05-16-2006, 02:23 PM

Quote:

Originally Posted by Dead Parrot

Good advice, Kovacs. But if you edit startx, then you'll have to do that again every time after you've upgraded Xserver.

It's better to create a file named .xserverrc into your home directory and add the xserverauthfile line there, like this:

Code:

#!/bin/sh
xserverauthfile=$XAUTHORITY

Then make .xserverrc executable (chmod +x .xserverrc).

doing this on debian/testing gives the following error

$startx
xauth: creating new authority file /home/fred/.serverauth.6509

giving up.
/usr/X11R6/bin/xinit: Connection refused (error 111): unable to connect to X server
/usr/X11R6/bin/xinit: No such process (error 3): Server error.
$

only after deleting the file was I able to startx again.

Dead Parrot · 05-16-2006, 02:50 PM

Yes, you're right -- I gave a bad advice.

Actually, you should make your .xserverrc to look something like this:

Code:

#!/bin/sh
xserverauthfile=$XAUTHORITY
exec /usr/bin/X11/X -dpi 96 -nolisten tcp

The "-dpi 96" part is not necessary, it just tells X server to use 96x96 dots per inch resolution.