On Tue, 14 Dec 2010, Rich Shepard wrote:
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.
True, if L123 was running at the time. Again, it's not been an issue over
It is very rarely "running". Each action is basically a new one, instance
based, non-persistent.
It doesn't really matter if you had Firefox open at the time--unless you
were in the process of loading a page, it would not be "running".
I think you mean "in mid process"--I.E. between two steps of a page load
or update.
Just because you aren't, doesn't mean that there is nothing left in a
state that would be effected adversely by an upgrade.
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.
I think you mistook my meaning a bit.
What I am suggesting, is that if the new version doesn't include all of
the same files that were in the old one, those old files won't be
overwritten. That could happen with code, just as much as templates.
Old version:
file1.pl
file2.pm
file3.x
file4.x
New version:
file1.pl
file2.pm
file4.x
file5.x
So, new version has dropped file3.x. However, your running version will
now have:
file1.pl
file2.pm
file3.x
file4.x
file5.x
So, code in file1.pl checks whether file3.x exists to determine whether it
is running in some particular configuration, that is compatible with the
old version.
That stale file is laying around from your old installation, and the old
behavior is triggered.
Again, I'm not saying that happens with SL or LSMB, I'm saying that as a
matter of policy, keeping all the old files that may not be there in newer
versions, can cause weird and sometimes very hard to track down problems.
Better to put the new version pristinely, and copy your templates, and
known compatible configuration data, in on top of it, instead of the other
way around.
That's what I was saying.
Luke
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
