| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Problems with events run |
Hello, Mike. Tuesday February 22 2011 at 21:20, you wrote to me: MT> You could have a primary node that exit with an errorlevel that points MT> to the real work. The rest exit with another errorlevel at the same MT> time that either quits completely (to be restarted by the primary node MT> at the end of the work routine) or goes into infinite loop on a MT> semaphore that is create by the primary at the start of the work and MT> deleted by the primary at the end of the work. That's a good idea, thanks! I'll have to implement that. Later, Sean ... You're never too old to learn something new. --- GoldED/2 3.0.1* Origin: Paragon BBS - 423.926.7999 - paragon.darktech.org (1:18/200) SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 18/200 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.