>I have a theory.
>Suppose the author of xlock was an idiot and used getlogin() to find the
>user's login name - fvwm will not have a controlling terminal or utmp entry
>and getlogin() will fail.
>
>Try this test:
> rsh yourhost /usr/openwin/bin/xlock -mode random
>If it fails the same way it's almost certainly a controlling tty problem.
Sorry, I ran
daneel:9> rsh daneel /usr/openwin/bin/xlock -mode random
and it locked the screen.
>
>Best solution (assuming I'm right - I may not be):
> - Fix xlock to use getuid(), not getlogin().
>
>Workaround:
> - Get your shell startup (.env for ksh, cshrc for csh, etc)
> or your first xterm to write the tty name (if any) to a well known
> file.load the name when you invoke xlock and attach
> #!/bin/sh
> # attach to a useful tty
> tty=`cat well-known-file`
> if [ ! -c "$tty" ]
> then echo "$0: $tty: not a tty" >&2; exit 1
> fi
> exec "$_at_" <"$tty" >"$tty" 2>&1
> and say
> Exec the-wrapper-above /usr/openwin/bin/xlock -mode rand
>
>Let me know how you go,
> - Cameron Simpson
> cameron_at_research.canon.com.au, DoD#743
> http://www.dap.csiro.au/~cameron/
>--
>The peever can look at the best day in his life and sneer at it.
> - Jim Hill, JennyGfest '95
>
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Jun 21 1996 - 10:17:42 BST