derstad@CIM-VAX.HONEYWELL.COM ("DAVE ERSTAD") (02/19/89)
I can handle a couple 3) Access node ID with a C procedure I use pm_$get_sid (look in /sys/ins/pm.ins.c for call sequence). Then just parse out the node ID. 8) Does the mark stack do anything useful Not that I've ever found. Probably only if you're really into DM programming. 10) Who cuts David Letterman's hair He does. If anyone else cut hair like that they'd be out of business.
achille@cernvax.UUCP (achille) (02/20/89)
1) About preventing window resizing, I guess you cannot do it.
3) getenv("NODEID");
5) have a look at the buffers in `node_data/paste_buffers, then use
pbufs calls to get their content.
7) use 'proc2_$who_am_i' to get the process uid (puid), then do
/com/ld -u `node_data/proc_dir
look at the output of /com/ld and if there is a uid == puid
then the corresponding name is the process name.
For your other questions, can't help.
Cheers, Achille Petrilli, Cray and PWS Operationsderstad@CIM-VAX.HONEYWELL.COM ("DAVE ERSTAD") (02/22/89)
The pst -c | fpat <active> approach to detecting a process wil no longer work at SR10.0. Since each program runs it it's own process, you will see some UID process, not the process calling the PST. The changed mode of execution messes up a large number of things, among them commands like "db" and "lkob". I suspect there are a number of latent problems/issues which will materialize only with time.