> I seem to remember a recommendation to use the individual commands instead > of the start_all command, to avoid a race condition where services would > start before their prequesites. In other words, at start up, run
This should no longer be an issue starting with 1.4 >> It seems that there may be a deeper problem here since I think Evergreen >> should start correctly at reboot, but this is a fix to get over this >> error. If Evergreen didn't get a chance to shutdown gracefully, it probably left around files referencing PID's, etc., and that might affect it when you try to start it back up. So after a reboot or some such, try restart_all as opposed to start_all. -- Jason Etheridge | VP, Community Support and Advocacy | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [EMAIL PROTECTED] | web: http://www.esilibrary.com
