>> If it is similar in GNU/Linux we have a general problem I suppose. If it is
>> a cygwin
>> thing, it is a feature which behaves different to the real posix world?!
> Cygwin is a POSIX environment executing within the Windows OS environment.
> If things happen outside of the Cygwin environment
>
> I scratch my head if we have a similar situation in GNU/Linux.
>
> If anything went havoc I so far supposed that exit code or abrupt script
> breakdown (stop) cares about not doing nasty things.
>
> So at the moment if you consider the OS or a user kills a process with
> Taskmanager we have
Hi Marco,
I agree and I didn't want to rant. I just consider robustness and I
can not rely on or guarantee that cygwin kill ist used. (It is the
user of the Windows machine being creative ;-)
I scratch my head if we have a similar situation in GNU/Linux.
If anything went havoc I so far supposed
On 12/23/2014 12:09 PM, - wrote:
Using Taskmanager is brute force as cygwin dll can not act and correctly manage
the exitcode
Hi,
thanks, but I do not agree. One element of the script was killed, not
the hoöe script.
It was not killed in the proper cygwin way.
> It should be more robust.
>> Using Taskmanager is brute force as cygwin dll can not act and correctly
>> manage the exitcode
Hi,
thanks, but I do not agree. One element of the script was killed, not
the hoöe script. It should be more robust. What I do now is: Read
stdout of the program (rsync) and only if I got the righ
On 12/23/2014 3:33 AM, - wrote:
Hi,
Any idea how to solve (get the "canceled" exit code? Remember: The
script continues like a normal finish of the command)
What do you mean by "canceled" exit code, pretty please?
oh, any exitcode <> 0 would be nice. Sending sigkill on debian gives a 137.
Hi,
>> Any idea how to solve (get the "canceled" exit code? Remember: The
>> script continues like a normal finish of the command)
> What do you mean by "canceled" exit code, pretty please?
oh, any exitcode <> 0 would be nice. Sending sigkill on debian gives a 137.
The point is, I rely on havin
Greetings, -!
> I have a script running banana after killing a process (rsync, but
> that is unimportant) through Taskmanager (End process in process tab).
> It is, that the killed process exits immediately with exitcode 0 (!)
> and the bash script itself continues, which can lead to havoc becau
Hi all,
I have a script running banana after killing a process (rsync, but
that is unimportant) through Taskmanager (End process in process tab).
It is, that the killed process exits immediately with exitcode 0 (!)
and the bash script itself continues, which can lead to havoc because
not knowing
9 matches
Mail list logo
