I fail to see a reason that the @restart is necessary after installation.
Looking at the archives, it apparently went in in 4.3, possibly as part of
the significant increase in use of @wait me in the command code; I'm
suspecting the @restart helped clear up any lingering issues with semaphores.
With jobs 6, we no longer use semaphores. The only functions I can see for
a @restart would be:
1. Trigger @startup. We can do this manually if we want, but I don't think
we actually need any startups anymore.
2. Force a save of the database after install. This is reasonable, but we
could just as easily @dump.
3. Force a reread of helpfiles. This can also be done with @readcache, but
really requires the user to have uploaded the jhelp.txt file and configured
it properly.
I think the @restart can/should be removed.
Original issue reported on code.google.com by widdis@gmail.com on 13 Feb 2010 at 7:42
Original issue reported on code.google.com by
widdis@gmail.com
on 13 Feb 2010 at 7:42