Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.


  Search this Thread
Old 04-20-2004, 02:15 PM   #1
LQ Newbie
Registered: Apr 2004
Posts: 7

Rep: Reputation: 0
kwrited and wall with 9.2 or 10.0?

I haven't been able to get the KDE kwrited to work with wall or write in any Mandrake release past 9.1. I'm running 9.1 at home and it works fine. I get get alerts just fine in KDE from apcupsd in the event of power outages.

I've noticed that, starting in 9.2, the /dev/pts/* devices belong to my own users default group rather than tty. I saw a post recommending that this be changed in /etc/devfsd.conf:

# Uncomment the following if you want to set the group to "tty" for the
# pseudo-tty devices. This is necessary so that mesg(1) can later be used to
# enable/disable talk requests and wall(1) messages.
REGISTER ^pty/s.* PERMISSIONS -1.tty 0600
#REGISTER ^pts/.* PERMISSIONS -1.tty 0600

Uncommenting that second line doesn't seem to work. After reboot, my /dev/pts/0 still belongs to my group. I'm not sure if that would address the problem anyway.

Also, while I understand the 'mesg y' command, I'm unclear how it relates to the DM or KDE. Is there a setting in the DM somewhere that enables write for that login?

The other unusual thing I've noticed is this: In 9.1, when a user is logged into X, the 'who' command shows two entries, one for pts/0 and one for the display :0. In 9.2 it shows only the entry for :0. In 10.0 it shows nothing at all....that one really doesn't seem right. Even if all permissions and everything were correct, write and/or wall won't work if it doesn't see the user logged in.

Any suggestions would be appreciated. Thanks!

Old 04-20-2004, 04:46 PM   #2
LQ Newbie
Registered: Apr 2004
Posts: 7

Original Poster
Rep: Reputation: 0
My mistake on that issue with 'who'. In 9.2 there's an entry for display :0...the entry for /dev/pts/0 was from a telnet login and had nothing to do with this.

It is strange though that loggin into KDE in 10.0 doesn't seem to get writen to wtmp.

Old 04-23-2004, 02:45 PM   #3
LQ Newbie
Registered: Apr 2004
Posts: 7

Original Poster
Rep: Reputation: 0
In trying to figure this out, I've discovered a few interesting things...

First of all, it appears that kwrited works listens to /dev/pst/0 (or whatever pts device the X session gets). If I log in as root and try:

echo testing > /dev/pts/0

...writed displays the message just fine.

The big problem does appear to be that, in 9.2 and 10.0, the pts device for the X session never gets into utmp. In 9.1 and prior it did. I can't figure out where this actually occurs in the older releases. The entry doesn't appear until the KDE is completely up and running.

In 9.2/10.0, without the sessions pst/* entered in utmp wall never finds it. Anyone have any idea if this can be configured somewhere??

Another potential issue is the group ownership of the device. Changing this line in /etc/fstab:

none /dev/pts devpts mode=0620 0 0
none /dev/pts devpts mode=0620,gid=5 0 0

...takes care of that, assigning /dev/pts/* to the tty group.

Here's the strangest thing I found: The default entries in the config file /usr/share/config/kdm/kdmrc used to define 'Startup' as /etc/X11/xdm/GiveConsole and 'Reset' as /etc/X11/xdm/TakeConsole. Since 9.2, these have been reversed. This adds display :0 for your user name when you log out of KDE.

Strange stuff. Anyway, if anyone has some idea where in the kdm and/or KDE login process the /dev/pts/0 would get added to utmp I'd like to know.

Old 04-28-2004, 09:32 AM   #4
LQ Newbie
Registered: Jan 2004
Location: Madrid (Spain)
Distribution: Mandrake
Posts: 5

Rep: Reputation: 0

answering to you just to thanks for the gid=5 trick wich enable "talk" for me again. I could make it work wifhout even rebooting thanks to "mount -o remount /dev/pts" after the change.

I could not answer to the other question, but to confirm that under gnome the behaviour is the same (i.e., no utmp entry for the /dev/pts/0 device).

Thanks again,
Old 04-28-2004, 10:15 AM   #5
LQ Newbie
Registered: Apr 2004
Posts: 7

Original Poster
Rep: Reputation: 0
Thanks for the reply. I think I now know what the issue is. kwrited grabs the pts device (/dev/pts/0 or whichever) and listens to that device, but doesn't add the pts device to utmp unless it's been compiled with utemper support.

As a result commands such as wall never find it. Apparently people have had similar issues with Debian. I get the impression that utemper is viewed by many developers as a bit of a hack, and they simply don't want to use it.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Harddrives on the wall Ephracis General 20 12-05-2004 04:20 PM
fire wall berrance Red Hat 2 08-21-2004 12:55 PM
[C++] -Wall Output noir911 Programming 2 08-01-2004 08:17 AM
Do I need a fire wall? shanenin Linux - Security 9 12-11-2003 02:21 AM
graphical wall? Tinkster Linux - General 15 11-29-2002 01:12 AM > Forums > Linux Forums > Linux - Distributions > Mandriva

All times are GMT -5. The time now is 12:15 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration