Not sure if this is the right place as the forum description says it's for 11.34. Anyway...
Since the upgrade to 11.36 cpbackup has been failing. Upon inspection, it has the old shebang path, not the new one (like other scripts in the same directory). Fixed it by hand (that horrendous bit of shell at the start) and ran the script, which worked.
Next day, the backup failed. The old shebang path (/usr/bin/perl) was back. Fixed it by hand and ran the script, which worked.
Next day, guess what? That's right.
Fixed it by hand again. Ran upcp (which was the obvious suspect) and it remained OK.
The setup was previously handled by somebody else who left the company before I joined. It's possible something he did is responsible for this, but I can't find it.
What I'm hoping is that you neglected to fix cpbackup at source, meaning that upcp kept putting the old version in place, and that you've now fixed the problem. That would mean I can stop looking. Or, it's still broken at source and something other than upcp is replacing cpbackup every night but now I've told you of the problem you'll fix it at source.
Keeping my fingers crossed...
--
Paul
Since the upgrade to 11.36 cpbackup has been failing. Upon inspection, it has the old shebang path, not the new one (like other scripts in the same directory). Fixed it by hand (that horrendous bit of shell at the start) and ran the script, which worked.
Next day, the backup failed. The old shebang path (/usr/bin/perl) was back. Fixed it by hand and ran the script, which worked.
Next day, guess what? That's right.
Fixed it by hand again. Ran upcp (which was the obvious suspect) and it remained OK.
The setup was previously handled by somebody else who left the company before I joined. It's possible something he did is responsible for this, but I can't find it.
What I'm hoping is that you neglected to fix cpbackup at source, meaning that upcp kept putting the old version in place, and that you've now fixed the problem. That would mean I can stop looking. Or, it's still broken at source and something other than upcp is replacing cpbackup every night but now I've told you of the problem you'll fix it at source.
Keeping my fingers crossed...
--
Paul