Yet another X problem (more precisely, scologin)
Diller
don't know how or when I may have messed up an OpenServer 5.0.5 system
that I inherited. It may never have been functional. The current
configuration does not permit anyone other than root to log in through
scologin on tty02. After taking the (non-root) UID and password, and
briefly blanking the screen, scologin reverts to the graphical SCO login
screen. However, if I complete a 'terminal' login on any other console
screen, and then manually run startx, almost everything is fine. The only
problem is that the "UNIX" resource (scoconsole?) just opens and
immediately closes the virtual terminal screen. Again, everything is fine
for root.
I have looked in syslog for messages, and done some elemental tracing. I
decided to back off when I noticed that the system Xstartup was nothing
but generic comments (effectively, a null file), and that the scologin
process didn't even get so far as to look at $HOME/.startxrc (determined
by access time). So I have no clue as to what is or should be happening.
It seems this is a matter of permissions, but I can't see where. Can
anyone even suggest a way to log the scologin process to determine where
the problem lies?
I would greatly appreciate any thoughts on the problem,
Diller
Fabio Giannotti
Diller <dr...@slonet.org> wrote in message
news:dryan-20110...@cas1-156.snlo.dialup.slonet.org...
It's possible that the accounts you are trying to log in as have "non-X
stuff" in their .profiles.
Try to create a brand new user from scoadmin, then try to log in as that
user. If you can log in, then the problem is indeed .profile related. If
you still can not log in, then I dont know!
Good luck,
Fabio
Jean-Pierre Radley
| Since I only occasionally use X, and then as root from the console, I
| don't know how or when I may have messed up an OpenServer 5.0.5 system
| that I inherited. It may never have been functional. The current
| configuration does not permit anyone other than root to log in through
| scologin on tty02. After taking the (non-root) UID and password, and
| briefly blanking the screen, scologin reverts to the graphical SCO login
| screen. However, if I complete a 'terminal' login on any other console
| screen, and then manually run startx, almost everything is fine. The only
| problem is that the "UNIX" resource (scoconsole?) just opens and
| immediately closes the virtual terminal screen. Again, everything is fine
| for root.
Check /usr/lib/X11/scologin for an Xerrors file.
Instead of hitting <ENTER> after entering the password, use the <F1> key
instead.
What shells are your users using?
--
JP
Dave Dickerson
>Since I only occasionally use X, and then as root from the console, I
>don't know how or when I may have messed up an OpenServer 5.0.5 system
>that I inherited. It may never have been functional. The current
>configuration does not permit anyone other than root to log in through
>scologin on tty02. After taking the (non-root) UID and password, and
>briefly blanking the screen, scologin reverts to the graphical SCO login
>screen. However, if I complete a 'terminal' login on any other console
>screen, and then manually run startx, almost everything is fine. The only
>problem is that the "UNIX" resource (scoconsole?) just opens and
>immediately closes the virtual terminal screen. Again, everything is fine
>for root.
>
>I have looked in syslog for messages, and done some elemental tracing. I
>decided to back off when I noticed that the system Xstartup was nothing
>but generic comments (effectively, a null file), and that the scologin
>process didn't even get so far as to look at $HOME/.startxrc (determined
>by access time). So I have no clue as to what is or should be happening.
>
>It seems this is a matter of permissions, but I can't see where. Can
>anyone even suggest a way to log the scologin process to determine where
>the problem lies?
>
>I would greatly appreciate any thoughts on the problem,
>Diller
I dimly recall that incorrect permission settings on
/tmp can sometimes cause this problem.
DDINAZ
Diller
If I had happened to find Xerrors before posting, I would have seen
something to the effect of "display :0 closed abnormally". And who knows
where that helpful message would have taken me...
The problem was that while root uses 'sh', my personal account is set for
'bash'. And when I had tried another generic account just to try a
different shell, the account I chose was set for 'rsh'. No go. After
JPR's message, I just copied Xsession-sh to Xsession-bash and was able to
log in from scologin. So that's a big gold star for Mr. Radley, and a
bucket of ashes for SCO.
And that was a great tip on the F1 login. Where else in the world would I
have learned that? I'm not quite sure how I might use that login mode,
but it's nice to learn about it.
I am still unable to use the UNIX button on my (non-root) desktop. The
virtual tty just opens and immediately closes. Root doesn't have any
problem. The F1 login does work from my personal account.
Thanks again,
Diller
Tom Parsons
| Wow! I can't imagine how much time you saved me. Thank you!
|
| If I had happened to find Xerrors before posting, I would have seen
| something to the effect of "display :0 closed abnormally". And who knows
| where that helpful message would have taken me...
|
| The problem was that while root uses 'sh', my personal account is set for
| 'bash'. And when I had tried another generic account just to try a
| different shell, the account I chose was set for 'rsh'. No go. After
| JPR's message, I just copied Xsession-sh to Xsession-bash and was able to
| log in from scologin. So that's a big gold star for Mr. Radley, and a
| bucket of ashes for SCO.
Huh? If you choose to install an unsupported shell, why is it SCO's
responsibililty to anticipate that action?
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Jean-Pierre Radley
|
| And that was a great tip on the F1 login. Where else in the world would I
| have learned that? I'm not quite sure how I might use that login mode,
| but it's nice to learn about it.
man scologin discusses 'failsafe' procedures.
| I am still unable to use the UNIX button on my (non-root) desktop. The
| virtual tty just opens and immediately closes. Root doesn't have any
| problem. The F1 login does work from my personal account.
Can't help you there. I use tcsh, and have no trouble using a Unix Icon
if and when I have a desktop. Normally, I run X with the panner, but
without the desktop, and open up about 12 scoterms in different windows
of the panner.
--
JP
Nick Cole
> virtual tty just opens and immediately closes. Root doesn't have any
> problem. The F1 login does work from my personal account.
>
> Diller
In 5.0.5, default TERM became "scoansi". The behavior of ScoTerm you
describe is consistent with
TERM having a different setting (say, "ansi"). Either set TERM=scoansi (in
your .profile) or add the line
*termName ansi
to /usr/lib/X11/app-defaults/msg/ScoTerm
Nick Cole
ni...@pacificcoastsystems.com
Diller
Are you saying rsh is unsupported? Second, if the precise facility (bash)
wasn't provided, but a similar extension could have been anticipated, SCO
should have at least provided a meaningful error message and not just
closed the session.
Yes, SCO deserves the criticism. As a matter of fact, they deserve to be
taken over by some company that can support its products.
Tom Parsons <c...@tegan.com> flamed:
> Diller enscribed:
Jean-Pierre Radley
| > Huh? If you choose to install an unsupported shell, why is it SCO's
| > responsibililty to anticipate that action?
| Gee, that was too smooth. I thought JPR let me off awful easy...
Really? DO NOT TOP-POST, it's a pain the ass.
| Are you saying rsh is unsupported?
Try running under X with rsh and let us know what you find.
| Second, if the precise facility (bash)
| wasn't provided, but a similar extension could have been anticipated, SCO
| should have at least provided a meaningful error message and not just
| closed the session.
Yeah, and it should do it in Lithuanian if that's where your paternal
grandfather was born?
| Yes, SCO deserves the criticism. As a matter of fact, they deserve to be
| taken over by some company that can support its products.
I'll resist the bait.
--
JP