On Tue, 14 Dec 2010, Luke wrote:
Tis nearly always a good idea to restart major supporting components when performing an upgrade or significant transition. Just as a matter of course.
Luke, True, if L123 was running at the time. Again, it's not been an issue over the past 6 years so I didn't expect to find problems this time.
Probably also a good idea not to just rsync the new tree over the old one--you tend to end up with old and pointless files laying around that way. If any of those files get checked for to trigger legacy behavior, you could potentially harm your usage experience.
I agree. That's why I just copy the new tree to the old tree. Existing files will be overwritten while my templates and other installation-unique changes remain untouched. The last L123 upgrade I did was from the git repository. I keep looking for those instructions but haven't found them. While I don't (yet) need any of the improvements there's no harm in keeping current, but I don't need a source repo copy here. Rich _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
