Re: [BProc] proc_pid_map badness

[Nicholas H. <he...@se...>]

On Tue, 2003-07-29 at 10:56, er...@he... wrote:
> On Tue, Jul 29, 2003 at 09:50:53AM -0400, Nicholas Henke wrote:
> > Hey Erik~
> > 	How are things on your end? Pretty well here. 
> > I am attempting to use the proc_pid_map to see all of the processes for
> > a user on a remote node, so that I can use bpsh to kill them. Some of
> > these processes are running via ssh, so of course they are not in the
> > bproc pid space. Can you tell me where I am going wrong ?
> 
> I'm a little fuzzy on exactly what you're trying to do here.  If you
> want to kill a process in the slave's process space from a process
> (kill) in the master's process space, that won't work.  You can't send
> signals across process spaces.  Even with process ID mapping turned
> off in /proc (proc_pid_map), the mapping still happens for system
> calls (fork, wait, kill).

*sigh* I really need to smack my crack dealer around -- it seems I am
not getting the good stuff anymore. Thanks for the explanation ;)

> The reason I have the option to turn off pid mapping is that it allows
> you to see what's going on on the node even if you can't directly fix
> it from within BProc.  I've had situations where some bit of the node
> boot-up stuff was spinning eating up 20% cpu for no apparent reason
> and the only way to see that was turning off pid mapping.
> 

Ok -- much more sense.

> btw, in case it wasn't clear:
> 
> proc_pid_map == 2:  Do mapping for all users
> proc_pid_map == 1:  Do mapping for users but not for root.
> proc_pid_map == 0:  Do mapping for nobody.

Nic
-- 
Nicholas Henke
Penguin Herder & Linux Cluster System Programmer
Liniac Project - Univ. of Pennsylvania