utmp entries when using login via kdm

utmp entries when using login via kdm

Post by je.. » Sun, 24 Dec 2000 11:18:23



I realize that this is not a kde specific
question, but I thought there might be a good kde
solution.

I'm running Redhat 7 using the default kde
provided (I believe 1.1.x).

I'm setup to service remote X terminals via XDMCP
direct protocol using kdm. When they log in via
this method, the utmp file is not updated, and
therefore utilities like who don't show anyone
logged in.

Is there a standard solution to this ? I know
that if you run plain vanilla xterms you can pass
+ut which forces a utmp entry to be written.
However, there's no guarantee that these users
will use an xterm of any kind.

Any help/suggestions would be appreciated.

Thanks in advance.

Jeri Donn

Sent via Deja.com
http://www.deja.com/

 
 
 

utmp entries when using login via kdm

Post by Adolfo Santiag » Sun, 24 Dec 2000 22:44:18


I'm interested in doing the same thing: servicing remote X terminals via
XDMCP. Could you refer me to some information on how to do it?

I'm sorry I can't offer any input about your issue.

Thanks.

Quote:>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<


when using login via kdm:
Quote:> I realize that this is not a kde specific
> question, but I thought there might be a good kde
> solution.
> I'm running Redhat 7 using the default kde
> provided (I believe 1.1.x).
> I'm setup to service remote X terminals via XDMCP
> direct protocol using kdm. When they log in via
> this method, the utmp file is not updated, and
> therefore utilities like who don't show anyone
> logged in.
> Is there a standard solution to this ? I know
> that if you run plain vanilla xterms you can pass
> +ut which forces a utmp entry to be written.
> However, there's no guarantee that these users
> will use an xterm of any kind.
> Any help/suggestions would be appreciated.
> Thanks in advance.
> Jeri Donn
> Sent via Deja.com
> http://www.deja.com/


 
 
 

utmp entries when using login via kdm

Post by je.. » Mon, 25 Dec 2000 15:30:04


I'm not sure of the environment that you're trying to do this in, but I
can tell you what I did.

First, we're accessing the Linux box via MS Windows based X servers. We
have them all set for XDMCP Direct/Inquire and point them to the
machine name/ip of the Linux box. We've also set them to either allow
multiple window managers to run (both Microsoft and KDE) or just run
the whole session in one window using the Linux (again in my case KDE
window manager/environment).

On the Linux side, I run the machine in run level 5 (edit /etc/inittab
and set the initdefault value to 5). That gives the console of the
Linux box a graphical login (kdm on my machine). In addition, if you
edit the config files in /etc/X11/xdm, you'll need to change entries
from the defaults in at least Xaccess and maybe also in Xresources.
Follow the comments at the top of the Xaccess file and you should be
okay. Also, you may have to change the line in the Xresources file that
controls what port XDM listens on for connections. On my system, it was
set to 0 which meant it would never hear anything. I commented it out
and now the default value seems to work fine.

Hope this helps. Feel free to ask again if you need more.

Jeri



> I'm interested in doing the same thing: servicing remote X terminals
via=
> =20
> XDMCP. Could you refer me to some information on how to do it?

> I'm sorry I can't offer any input about your issue.

> Thanks.

> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<


entries =

> when using login via kdm:

> > I realize that this is not a kde specific
> > question, but I thought there might be a good kde
> > solution.

> > I'm running Redhat 7 using the default kde
> > provided (I believe 1.1.x).

> > I'm setup to service remote X terminals via XDMCP
> > direct protocol using kdm. When they log in via
> > this method, the utmp file is not updated, and
> > therefore utilities like who don't show anyone
> > logged in.

> > Is there a standard solution to this ? I know
> > that if you run plain vanilla xterms you can pass
> > +ut which forces a utmp entry to be written.
> > However, there's no guarantee that these users
> > will use an xterm of any kind.

> > Any help/suggestions would be appreciated.

> > Thanks in advance.

> > Jeri Donn

> > Sent via Deja.com
> > http://www.deja.com/

Sent via Deja.com
http://www.deja.com/
 
 
 

utmp entries when using login via kdm

Post by Nikita V. Youshchenk » Mon, 25 Dec 2000 17:55:17


Quote:> I realize that this is not a kde specific
> question, but I thought there might be a good kde
> solution.

> I'm running Redhat 7 using the default kde
> provided (I believe 1.1.x).

> I'm setup to service remote X terminals via XDMCP
> direct protocol using kdm. When they log in via
> this method, the utmp file is not updated, and
> therefore utilities like who don't show anyone
> logged in.

> Is there a standard solution to this ? I know
> that if you run plain vanilla xterms you can pass
> +ut which forces a utmp entry to be written.
> However, there's no guarantee that these users
> will use an xterm of any kind.

> Any help/suggestions would be appreciated.

Read 'man sessreg'
Seems that sessreg is not called for your remote sessions.
Try fixing script that is run (as root, not as user) after user enters
login and password. `man xdm` or similar will help you to find what
exactly script runs on your system.

Nikita

 
 
 

utmp entries when using login via kdm

Post by Adolfo Santiag » Mon, 25 Dec 2000 23:44:23


Thanks for the information.  It's going to take me some time to digest
this, so if I have any questions, it will be a while.

Again, thanks.

Quote:>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<


entries when using login via kdm:
> I'm not sure of the environment that you're trying to do this in, but I
> can tell you what I did.
> First, we're accessing the Linux box via MS Windows based X servers. We
> have them all set for XDMCP Direct/Inquire and point them to the
> machine name/ip of the Linux box. We've also set them to either allow
> multiple window managers to run (both Microsoft and KDE) or just run
> the whole session in one window using the Linux (again in my case KDE
> window manager/environment).
> On the Linux side, I run the machine in run level 5 (edit /etc/inittab
> and set the initdefault value to 5). That gives the console of the
> Linux box a graphical login (kdm on my machine). In addition, if you
> edit the config files in /etc/X11/xdm, you'll need to change entries
> from the defaults in at least Xaccess and maybe also in Xresources.
> Follow the comments at the top of the Xaccess file and you should be
> okay. Also, you may have to change the line in the Xresources file that
> controls what port XDM listens on for connections. On my system, it was
> set to 0 which meant it would never hear anything. I commented it out
> and now the default value seems to work fine.
> Hope this helps. Feel free to ask again if you need more.
> Jeri


> > I'm interested in doing the same thing: servicing remote X terminals
> via=
> > =20
> > XDMCP. Could you refer me to some information on how to do it?

> > I'm sorry I can't offer any input about your issue.

> > Thanks.

> > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<


> entries =

> > when using login via kdm:

> > > I realize that this is not a kde specific
> > > question, but I thought there might be a good kde
> > > solution.

> > > I'm running Redhat 7 using the default kde
> > > provided (I believe 1.1.x).

> > > I'm setup to service remote X terminals via XDMCP
> > > direct protocol using kdm. When they log in via
> > > this method, the utmp file is not updated, and
> > > therefore utilities like who don't show anyone
> > > logged in.

> > > Is there a standard solution to this ? I know
> > > that if you run plain vanilla xterms you can pass
> > > +ut which forces a utmp entry to be written.
> > > However, there's no guarantee that these users
> > > will use an xterm of any kind.

> > > Any help/suggestions would be appreciated.

> > > Thanks in advance.

> > > Jeri Donn

> > > Sent via Deja.com
> > > http://www.deja.com/

> Sent via Deja.com
> http://www.deja.com/

 
 
 

utmp entries when using login via kdm

Post by je.. » Tue, 26 Dec 2000 10:17:11


Thanks. It looks like you've exactly got it correct. Now, I'm off to
figure out why sessreg is only getting called or only working if you
login via xdm on the console.

Jeri



Quote:> > I realize that this is not a kde specific
> > question, but I thought there might be a good kde
> > solution.

> > I'm running Redhat 7 using the default kde
> > provided (I believe 1.1.x).

> > I'm setup to service remote X terminals via XDMCP
> > direct protocol using kdm. When they log in via
> > this method, the utmp file is not updated, and
> > therefore utilities like who don't show anyone
> > logged in.

> > Is there a standard solution to this ? I know
> > that if you run plain vanilla xterms you can pass
> > +ut which forces a utmp entry to be written.
> > However, there's no guarantee that these users
> > will use an xterm of any kind.

> > Any help/suggestions would be appreciated.

> Read 'man sessreg'
> Seems that sessreg is not called for your remote sessions.
> Try fixing script that is run (as root, not as user) after user enters
> login and password. `man xdm` or similar will help you to find what
> exactly script runs on your system.

> Nikita

Sent via Deja.com
http://www.deja.com/
 
 
 

1. shadow login: 'No utmp entry ...' - what now?

I had earlier reported problems with shadow-960129 on my system where it
was impossible to log in on the system console because of "missing utmp
entries"...  I have discovered a resolution to my problem.

I've filled up my var partition :-) with symlinks from /var/adm/utmp and
/var/log/utmp (and /etc/utmp) pointing to /var/run/utmp in an attempt to
satisfy all of the various levels of software packages I run that can't
agree on where this file is located.

I discovered, by accident, that /etc/rc.d/rc.S distributed in older
versions of Slackware (maybe newer, too, I don't know) deletes and
recreates /var/adm/utmp, thus destroying my link. Apparently, whatever
sets up utmp information for login was stuffing it in /var/adm/utmp and
then the shadow login was looking in /var/run/utmp and not finding it.

I never would have found this except that this "maintenance" in rc.S is
attempted *BEFORE* non-boot partitions are mounted, and I started getting
these error messages when I split /var off to a separate partition...

Cheers,

  Scott

----------


EDS / ESC - Detroit            313-556-6011 [8/346]

2. Script for displaying process tree?

3. Linux HOWTO Index (part 1/1)

4. No utmp entry for autoppp logins (redhat 5.1)

5. SOCKS on AIX

6. HELP:Can not Login: No utmp entry !!!

7. MGA Millennium

8. Problems login in: ODT 5.02 - "No utmp entry" : STUCK.

9. Cannot do login: "No utmp entry."

10. login: No utmp entry...

11. no utmp entry--you must run login from lowest level sh

12. can't login / no utmp entry / 0.99 p6