Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!inesc!unl!unl!jpc From: jpc@fctunl.rccn.pt (Jose Pina Coelho) Newsgroups: comp.windows.x Subject: Wish list R5 Message-ID: Date: 20 Jul 90 17:35:34 GMT Sender: news@fctunl.rccn.pt (USENET News System) Distribution: comp Organization: Universidade Nova de Lisboa -- Lisbon, Portugal Lines: 35 Today I had a server crash, it dumped the core and prompted for my password again. So far so good. But when my .clients finished another window poped into existance: the xterm of the previous session, running perfectly with the correct history. I'm shure that it's the previous window, because it's pid is inferior to the xserver. This is one *BIG* security hole. The xterm should have died immediately. I see one possible method: When a server comes up it broadcasts a message I'm_up(mach:disp.scr) When some aplication that is connected screen mach:disp.scr receives such a packet It should call an handle. The handle should have a default behavior of { printerror, exit(err) } However, things like xconsole should have a recovery procedure to try to reopen the screen as the driver comes up. I work with a VAX3100, (sg driver) between login and the launching of xconsole, any write to /dev/console will (90% of the time) scramble the cursors. (weird, I know) -- Jose Pedro T. Pina Coelho | BITNET/Internet: jpc@fctunl.rccn.pt Rua Jau N 1, 2 Dto | UUCP: jpc@unl.uucp 1300 Lisboa, PORTUGAL | ARPA: jpc%hara.fctunl.rccn.pt@mitvma.mit.edu Home phone: (+351) (1) 640767 - If all men were brothers, would you let one marry your sister ?