Quote:
Originally Posted by vigilandy
So by action, you mean clicking on an icon with your mouse, and by signal, you mean the bat signal, right? </sarcasm
|
No , let me explain it better .
obviously i'm posting in the SERVER forum so the issue is related to SERVERS , so no mouse clicking is involved instead an event or signal should be understood in terms of interprocess communication methods.
here is an example to illustrate the situation ,
assume you've a linux or a unix-like system with process A and B.
process A is doing random operations of some nature , however on certain occasions process A will divert special batch jobs (i.e computationally intensive jobs that are out of the scope of process A) to a different process namely B which will carry out those batch operations.
said that , process B will start those batch operations and run them to the end independently , while process A continues its normal operations without waiting for process B to return the output of those batch operations since they are no longer the concern of process A ....etc
yeah that's it basically.
now the difference between that and a cronjob , is that cron obviously it's period-driven while this server solution should be event driven , responding on demand whenever needed.
so far i've been experimenting with nohup and simple shell scripts but they way too unstable and very hard to debug..
cheers
thanks