[2136] in SIPB bug reports

home help back first fref pref prev next nref lref last post

xscreensaver

daemon@ATHENA.MIT.EDU (Marc Horowitz)
Thu Oct 3 19:06:04 1991

To: bug-sipb@Athena.MIT.EDU
Reply-To: Marc Horowitz <marc@MIT.EDU>
Date: Thu, 03 Oct 91 19:05:09 EDT
From: Marc Horowitz <marc@Athena.MIT.EDU>

The message

xscreensaver: couldn't bind to port 32253: Address already in use

is not useful for most users.  I just ran into a user who got this
message, so he ran xscreensaver again.  And again.  He was running six
xscreensavers.  Is it reasonable to require an option for xscreensaver
to run if it can't bind the port?  This would prevent this from
happening in the future.  Also, make the message better.  Perhaps:

xscreensaver: couldn't bind to port 32253: Address already in use
Are you already running xscreensaver?

		Marc

home help back first fref pref prev next nref lref last post