lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Hi Luiz,

The standard Lua interpreter does not handle SIGQUIT. You can either
change it or use your own Lua host. You can also try to do signal
handling using luaposix.

You means it rely on underlying OS to handle signals, right ? Because I can confirm that even a non interactive Lua program can be stopped by a SIGINT or a SIGQUIT (at least under Linux).

Anyway, as per my reading, closelog() is only needed for shared object and if custom ident is used (which is not my case). So a dirty quit is enough for now ; in a future version, I'll intercept SIGQUIT to avoid to interrupt in the middle of data transmission.