<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">With all the discussion adding registration,
passwords, with updated country files, bad this and that, etc.,
now being included with frequent new builds, and 'shut' from
crontab taking at least a minute to complete, what would it take
to hold users and connections over this restart period akin to a
'sleep' command? A new internal command, say, 'shut4update', would
pause the restart for 60 seconds, allow the spidercron clock to
increment, suspend or lengthen timeouts so not to drop or
disconnect.<br>
<br>
The benefit: Users, sometimes hundreds at once, would not need to
reconnect with passwords; loss of access would typically be only
10-20 seconds, and missed by much of the contest software out
there.<br>
<br>
I am not a coder. If I knew a little more about perl than I do now
I would be dangerous.<br>
<br>
73, John W1AN<br>
<br>
</font>-Feb-23 06:44, Kin EA3CV wrote:<br>
<blockquote type="cite"
cite="mid:892352CC-2FF7-1A4C-B3DF-EA4D0A151CB3@hxcore.ol">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">John, Also some updates do not require restart<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">By creating a new script and putting it in the
local_cmd folder, this new script becomes an internal spider
command. </div>
<div dir="auto">If no one gives a better solution, I can send it
to you to try. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Kin EA3CV<br>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div id="ms-outlook-mobile-signature" dir="auto">Enviado desde <a
href="https://aka.ms/AAb9ysg" moz-do-not-send="true">Outlook
para Android</a></div>
</blockquote>
<br>
</body>
</html>