[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

2775.0. "Why owner cant kill xterm?" by FORTSC::SHOMO () Wed May 16 1990 16:55

    A customer has asked why under DECwindows/UWS 2.2 a xterm process
    started under DECterm can not be killed by the owner? One has to become
    super-user to succesfully kill the xterm child process. Is this due to
    its effective owner-Id being something other than what appears in
    ps(1)?
    
    Any takers?
    Rob-

T.R Title User Personal
Name Date Lines

2775.1 ABYSS::dike Wed May 16 1990 17:04 8

T.R	Title	User	Personal Name	Date	Lines
2775.1		ABYSS::dike		`Wed May 16 1990 17:04`	8
	xterm is setuid root. I think that is for purposes of updating utmp. You can cause xterm to exit by using exit off the ctrl-mb2 menu if you can't get rid of the shell it's running. If you are looking for a non-interactive way of killing xterms make a setuid script to do it. Jeff

xterm is setuid root.  I think that is for purposes of updating utmp.

You can cause xterm to exit by using exit off the ctrl-mb2 menu if you can't
get rid of the shell it's running.

If you are looking for a non-interactive way of killing xterms make a setuid
script to do it.
				Jeff