Since startx is itself a script, you could modify it to use always a
system-wide xinitrc, and have that run xlock & then ~/.xinitrc.
Provided your users are docile. There is nothing to stop them starting
x with xiniit, or even X :0, and that is what I would do if someone
tried to foist xlock on me. :-). You could, of course, restrict access
to X, but as you can't suid a script, you would need an executable to
take on the tasks of your site-local X startup.
If you want any kind of security with X, you probably want to look into
xdm. It runs a system-wide Xsession, which normally runs ~/.xsession.
I don't see why it couldn't do an xlock & first.
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
On Fri, 16 Apr 1999, Nagle, Adrian wrote:
> I'm curious to learn how to make sure each user starts an xlock
program. I
> could ask that everyone put it in their .xinitrc, but then I depend on
the
> user doing that and not changing it.
>
> I'm curious to know if there is a way for some system "standard" to
startup
> and then the user can configure their .xinitrc at will.
>
> Is there a standard file or location that should be sourced in the
.xinitrc
> or vice versa?
>
> Thanks
>
> Adrian
> --
> Adrian Nagle Ball Aerospace & Technologies Corp.
> Thermal Engineer P.O. Box 1062
> TEL: 303-939-6518 Boulder, CO 80306-1062
> FAX: 303-939-5166 http://www.ballaerospace.com
>
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
