Changes
no edit summary
If you check this box, the service will stop when everything is executed.
== Offline Mode ==
(previously discussed as the "laptop mode")
Some of you complained that if logon delay is enabled and the server is unreachable (because that client machine is a laptop unplugged from a network), users have to wait for too long. This happens for several reasons - trying to resolve DNS name, wrong routing etc.
The idea with "offline mode" is to try to reach a server for few seconds (3 seconds default, configurable), and if it fails (no connection, no reply etc.), discontinue further execution (skip logon delay, don't execute any actions).
Here we have two configurable options:
* server IP or name, OR
* custom script - execute a custom scrip/program; if it exits with a non-zero code, consider it a failure. The rationale behind a custom script is that a client can have a connection to the server, but it's a slow dial-up connection. Installing something big over a dial-up is certainly not a good idea. Of course, it is up to the administrator to write such a custom script.
Both options can have maximum waiting time specified.
NOTE: the "server IP or name" tries to connect to the server using port 139 - obviously, the server has to listen on this port.
NOTE2: the "server IP or name" will currently report a success if it gets *any* packet back from the server (like RST). It should only report success if it receives a SYN packet - this should change before a final release.