| 1 |
On Sun, 7 Feb 2021 14:01:57 -0700, thelma@×××××××××××.com wrote: |
| 2 |
|
| 3 |
> >>>>> [ -z "$SSH_TTY" ] && startx ... |
| 4 |
> >>>>> |
| 5 |
> >>>>> to only start it when not using SSH. |
| 6 |
> >>>> |
| 7 |
> >>>> What do you suggest? |
| 8 |
> >>>> I was planning to get away from "slim" as I think it is getting |
| 9 |
> >>>> more unstable; I just need a simple system to start X, log-in over |
| 10 |
> >>>> ssh and use x2go session. |
| 11 |
> >>> |
| 12 |
> >>> Why do you need to start X, doesn't x2go run its own X session? You |
| 13 |
> >>> are trying to start X in an SSH session, which is what gives your |
| 14 |
> >>> error. The line I suggested runs startx only if you are not logging |
| 15 |
> >>> in via SSH. No display manager is involved. |
| 16 |
> >> |
| 17 |
> >> Maybe I wasn't clear. No, I don't start any X over ssh. |
| 18 |
> > |
| 19 |
> > But you do, because you run it from .bash_profile whenever you login. |
| 20 |
> > That's why I suggested an alternative command that wouldn't do that. |
| 21 |
> |
| 22 |
> OK, according to Gentoo-wiki: |
| 23 |
> https://wiki.gentoo.org/wiki/Start_X_on_login |
| 24 |
> |
| 25 |
> ~/.bash_profile |
| 26 |
> if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startx; fi |
| 27 |
> The above command works. |
| 28 |
|
| 29 |
It is effectively the same as the one I suggested right at the start of |
| 30 |
this thread. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Neil Bothwick |
| 35 |
|
| 36 |
Windows95 - crash compatible on Windows 3.x |
Archives