Re: bin/53049: wsmoused not working: ioctl(WSDISPLAYIO_PUTWSCHAR) fail

[bernward.pub%arcor.de@localhost]

The following reply was made to PR bin/53049; it has been noted by GNATS.

From: bernward.pub%arcor.de@localhost
To: gnats-bugs%NetBSD.org@localhost
Cc: mlelstv%serpens.de@localhost
Subject: Re: bin/53049: wsmoused not working: ioctl(WSDISPLAYIO_PUTWSCHAR) fail
Date: Sun, 25 Feb 2018 12:49:40 +0000 (UTC)

 Hello Michael,
 
 I tested this and can confirm that setting the right X console in
 /etc/wsmoused.conf makes wsmoused quiet, when I switch to X.
 So, with the right set configuration file /etc/wsmoused.conf,
 there are no more disturbances to the use of X.
 
 Again, the classification of this PR should be unchanged, because
 the intended function of wsmoused is still not given at all,
 while it disturbs the text console by unnecessarily using cpu time.
 
 A possibly interesting observation aubout the used cpu time of wsmoused
 and syslogd via top, now with the right setting only on text console:
 Heavy mouse movements for about 5 seconds let both values go up over 40% cpu usage.
 While then I do not touch the mouse any more, I can see an exponential-like
 fall of both usages, which needs over 30 seconds to fall below 1.00%
 and after 1min ist at 0.00% for both.
 
 Best regards, Bernward. 
 
 
 On 2018-02-25 10:44, Michael van Elst wrote:
 > wsmoused is supposed to co-exist with the X server by releasing mouse
 > control when you switch to the X display and regaining mouse control
 > when you switch back to a text console. There is a configuration file
 > /etc/wsmoused.conf that can be used to tell it which display is used
 > by X. It is supposed to handle only one X display and I don't know if
 > that actually works.