Vine Server 3.0 killed on logout, messy solution

Vine
1

I have the same problem with Vine Server 3.0 run as a system service on 10.4.11 and 10.4.11 server. On logout the service is killed, with the following in the osxvnc_exit.log:

2008-07-29 13:36:43 Server exited with result: 137
2008-07-29 13:36:48 Server exited with result: 134
2008-07-29 13:36:53 Server exited with result: 134
2008-07-29 13:36:58 Server exited with result: 134
2008-07-29 13:37:03 Server exited with result: 134
2008-07-29 13:37:09 Server exited with result: 134
2008-07-29 13:37:09 The same error ‘134’ happened 5 times in a row, not restarti
ng!

The 134 turns out to be an ABORT signal, so I modified the line in the keep-alive script that checks for the 137 signal to also ignore the 134:

if [ “$RESULT” -ne “137” -o “$RESULT” -ne “134” ]

That seems to have solved it, but seems messy. Is this a known problem? Was there an OS update that changed the signals sent?

2

I’m not certain if that was an OS update but I think that’s a perfectly fine patch to leave in there.

I’m personally not seeing that behavior (in that way) but I don’t think having that other code excluded is going to cause any harm and so I’ll probably apply it to the script globally.