From: <ha...@no...> - 2002-05-22 15:58:05
|
Hi, me again :-) Seemes to be possible to let this always hold for masq-ed process: current->pgrp == current->bproc.masq->pgrp current->session == current->bproc.masq->session (these values therefore mostly differ from current->pid) Looks strange at first, some basic BProc ideas seemes to be shaken, but it may be workable approach. Comments welcome, of course. There are hunderds of places where pgrp/session is used in some way. No chance to even look at all of them. However there are just few places where kernel compares pid to pgrp/session. Should be easy to fix any broken details. I modified masq_setsid() and masq_setpgid() to also save new values to normal pgrp and session and things look promissing. Now I can login to node via ssh without any complaints, run some commands and try to logout - where it hangs now (in select(), do not have details yet). Now it also complains (on master) once per every command run from login bash: kernel: bproc: ghost(2124): failed to wait on 2132.options=2 err=-10 But I guess I would work these things out. Most of all, I would like to here your comments on the idea of using master's pgrp and session also in normal non-masq-ed process information on slave. Best Regards Vaclav |