I just do something like
exec startx
and not have to worry about somebody trying to get in by killing the
process or stopping it or whatever...
Once you kll the X session, you automatically get logged out.
-Naren
On Thu, 31 Jan 2002, Philip S Tellis wrote:
> Sometime on Feb 1, USM Bish assembled some asciibets to say:
>
> > > Although the preferred way to do it (according to the man
> > > page) is:
> > >
> > > startx &>startx.log
> > >
> > ---end quoted text---
> >
> > Thanks Philip, additions incorporated ...
>
> Of course, I do
> startx &>.xsession-errors &
> looks better, creates a hidden file, and gives me my terminal back.
>
> If I didn't do it, and I locked my screen and went away, someone could
> come to my terminal, Ctrl+Alt+F1 and kill my X session. Instead, I get
> back to my terminal, and run vlock.
>
> Some may point out that I could just logout instead of running vlock.
> But, this isn't a good idea if you look at /etc/security/console.perms
>
> When I log out, I lose ownership of the console - even if I have
> processes running. That means that I no longer have permission to use
> the sound device for one. The sound device strangely seems to be
> accessed from certain libraries that are linked into - above all things
> - gvim. I spend 90% of my time using gvim.
>
> It also causes other problems - like not having a controlling tty if I
> su.
>
> --
> Following the rules will not get the job done.
>
>
> _______________________________________________
> linux-india-help mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/linux-india-help
>
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
