Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jul 2003 20:02:53 -0400
From:      "Gerald S. Stoller" <gs_stoller@hotmail.com>
To:        freebsd-questions@freebsd.org
Subject:   xterm
Message-ID:  <Sea1-F77KUsqPQx0gdE0000bf0a@hotmail.com>

next in thread | raw e-mail | index | archive | help
FreeBSD  4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001
jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC  i386

	When working in a  Unix  system, I like to work with several windows (if 
possible) and organize my work among them.  I use  xterm  (as on the line 
'xterm  &') to open new windows.  Recently, I wanted to check on my 
processes and issued the command 'ps -l' and was surprised to not find any  
xterm processes among them.  So I issued the command 'ps -la' and there I 
found the  xterm  processes but they were owned by  root , not by me who had 
issued the command.  Even though I wasn’t listed *by the ‘ps –la’ command as 
the owner, I could still kill the  xterm  processes.  I don’t know where the 
incongruity is, in the  kernel’s  tables or in the reporting by  ps .
	In multi-user (commercial) systems, I believe that the user who invokes the 
  xterm  processes is (listed as) its owner.
	I prefer that all processes running in  FreeBSD  be owned by the user who 
invoked them, the exceptions being some system ( root ) processes used in 
the  login  process.  (The  xterm  processes are included here as non-system 
processes, so they should be owned by the user who invoked them.)  I would 
like to see  FreeBSD  changed to reflect this, but the bug reporting site is 
down now.  If anyone knows of any reasons why the current operation is 
correct and should be left as is, please inform me.

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Sea1-F77KUsqPQx0gdE0000bf0a>