The circumstances needed to recreate the extended shut-down are mounted network shares, and a wireless connection.
Tested and working fine now; thanks.
we fixed this in antiX 13 and 15. sam reminded me. I'm looking for the fix as we speak.
Thanks for picking up the ball on this.
Referring back to February 2014; at that time a web search revealed large numbers of Debian users were reporting the problem of a pause during shut-down. A fix was not introduced by Debian and is unlikely to be following the move to systemD. antiX inherited the unwanted behaviour because of its Debian parentage, and it remains in place because of our retention of sysvinit.
Connectshares cannot avoid a problem of that nature and is not causing it. Shares mounted via standard Linux mount techniques (i.e. not using helpers such as Connectshares) also exhibit the pause symptoms at shut-down if they are not unmounted before beforehand. The unwanted behaviour originates from upstream Debian.
The problem stems from the sequence in which the Debian init.d system stops services. The short version is, wireless networking is stopped before shares are unmounted. In turn this generates the time-out delay later in reboot/shut-down process.
The standard Debian file at the heart of the problem is / etc/init.d/umountnfs.sh. Its purpose is shown in the following abstract from the file.
# Short-Description: Unmount all network filesystems except the root fs.
# Description: Also unmounts all virtual filesystems (proc,
# devpts, usbfs, sysfs) that are not mounted at the
# top level.
The previously submitted fix is named unmountnfs-alternative.sh. It is identical to unmountnfs.sh except for one minor amendment. Towards the head of the file, "Provides" now indicates "umountnfs-alternative". The fix runs its links earlier in the init.d sequence which prevents the pause condition and allows the reboot/shut-down to continue without a delay.
The result is neutral for systems that do not have the initial problem, beneficial for those that do, and transparent for all.
New connectshares deb soon to appear in repo to (hopefully) fix this problem
Probably it is best to implement the fix outside of Connectshares. Because this problem is not caused by Connectshares, it will be of most benefit when the fix is not tied to it. In that way the fix will be available to systems which use share mounting techniques other than Connectshares. Perhaps incorporating it into the basic antiX build might be a better approach.