well this is nice but it only shows the eggdrop.exe pid ?? And not the pid of an exec filename.exe .... nice to know but not exaclty what i was looking for hehe
You should have asked about getting the pid of the new process then. As a matter of fact, you can, but as it says on the help page for "pid" you can't do it with exec. Use the "open" command to run the program and then use the "pid" command with the file handle that open returns to get the child process's pid.
set fp [open "|someprogram arg1 arg2" "r+"]
putserv "privmsg #sheep :pid of child is [pid $fp]"
You'll have to change your program some because open and exec work a bit differently.
oh it is like monitor .. ? like if your gone do lots of stuff with the file or refering to the to the file .. you can use this ?? open thing ? then exec ... ?
hmm i think i know what you mean and its not a while but it seems if i use open the eggy keeps open the file ... so wen it ends it is still running but .. the program is not active no more so .. ? maybe it is an error in the exe it self :/ don't realy know but it should close by it self .. :/ it normaly does, is it possible that the eggy keeps the file open ?