David Stringfield
2017-04-11 01:23:11 UTC
Dear all,
How's it going?
I have a centos server we use for backup. I was having some trouble with
rsnapshot recently and after much (much) fiddling, I finally realised that
~somehow~ the file /usr/bin/rsnapshot had been wiped. It existed, but was
an empty file (I'm guessing that in my ridiculous midnight delirium I
somehow wiped the file myself, hence why I'm saying ~somehow~ :/ )
So I took the file rsnapshot-program.pl directly from the github project,
copied it into the same directory as my (now empty) rsnapshot file, and
then overwrote the empty rsnapshot file with the fresh one, changing the
name from "rsnapshot-program.pl" to "rsnapshot" in the process. One thing
I tried to be wary of here is how SeLinux may block this, hence why I did
the specific overwriting.
I then ran the rsnapshot command straight from the terminal, and got an
error about the Perl interpreter, which was obviously still @PERL@ in the
file. I am no expert on scripting but I figured that this was a compiler
reference, so I updated it to my system's Perl directory. Viola! When I
typed in the command I got the usual output:
rsnapshot @VERSION@
Usage: rsnapshot [-vtxqVD] [-c cfgfile] [command] [args]
Type "rsnapshot help" or "man rsnapshot" for more information.
With the one exception about the @***@. Now I'm guessing that a
missing the correct version reference shouldn't matter too much.
MY QUESTION: Is there anything else like the @VERSION@ or the @PERL@ that
I need to change also that could break it? I've run it with -t and with
configtest options and the results are as I expected.
Hope to hear back from you and thanks for your time,
David Stringfield
IT Support
E: ***@wmawater.com.au
<http://www.wmawater.com.au/>
Please consider the environment by not printing this email.
The information contained in this email may be confidential. You should
only disclose, re-transmit, copy, distribute, act in reliance on or
commercialise the information if you are authorised to do so. WMAwater
does not represent, warrant or guarantee that the communication is free of
errors, virus or interference.
How's it going?
I have a centos server we use for backup. I was having some trouble with
rsnapshot recently and after much (much) fiddling, I finally realised that
~somehow~ the file /usr/bin/rsnapshot had been wiped. It existed, but was
an empty file (I'm guessing that in my ridiculous midnight delirium I
somehow wiped the file myself, hence why I'm saying ~somehow~ :/ )
So I took the file rsnapshot-program.pl directly from the github project,
copied it into the same directory as my (now empty) rsnapshot file, and
then overwrote the empty rsnapshot file with the fresh one, changing the
name from "rsnapshot-program.pl" to "rsnapshot" in the process. One thing
I tried to be wary of here is how SeLinux may block this, hence why I did
the specific overwriting.
I then ran the rsnapshot command straight from the terminal, and got an
error about the Perl interpreter, which was obviously still @PERL@ in the
file. I am no expert on scripting but I figured that this was a compiler
reference, so I updated it to my system's Perl directory. Viola! When I
typed in the command I got the usual output:
rsnapshot @VERSION@
Usage: rsnapshot [-vtxqVD] [-c cfgfile] [command] [args]
Type "rsnapshot help" or "man rsnapshot" for more information.
With the one exception about the @***@. Now I'm guessing that a
missing the correct version reference shouldn't matter too much.
MY QUESTION: Is there anything else like the @VERSION@ or the @PERL@ that
I need to change also that could break it? I've run it with -t and with
configtest options and the results are as I expected.
Hope to hear back from you and thanks for your time,
David Stringfield
IT Support
E: ***@wmawater.com.au
<http://www.wmawater.com.au/>
Please consider the environment by not printing this email.
The information contained in this email may be confidential. You should
only disclose, re-transmit, copy, distribute, act in reliance on or
commercialise the information if you are authorised to do so. WMAwater
does not represent, warrant or guarantee that the communication is free of
errors, virus or interference.