Re: [BackupPC-users] Rename of directories error and other oddities...

All my backups seemed to have worked... I check this morning and it looks
good, I will try some restores later on and see how it goes...

Anyone see a problem if i leave it this way?

As i have not touched or altered anything other than doing standard apt-g
upgrade on the box.... SO i am not sure why this command would stop working
due to this particular error....



Rob Morin
Senior Systems Administrator
Momentum Ventures
(514) 508-7500 Ext 207


-----Original Message-----
From: Holger Parplies [mailto:wbppc AT parplies DOT de] 
Sent: May-07-14 8:49 AM
To: backuppc AT kosowsky DOT org
Cc: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Rename of directories error and other
oddities...

Hi,

backuppc AT kosowsky DOT org wrote on 2014-05-06 20:37:48 -0400 [Re:
[BackupPC-users] Rename of directories error?and?other?oddities...]:
> Holger Parplies wrote at about 01:48:55 +0200 on Wednesday, May 7, 2014:
>  > Rob Morin wrote on 2014-05-06 15:02:34 -0400 [Re: [BackupPC-users]
Rename of directories error and?other?oddities...]:
>  > > To fix the issue I simply did the following...
>  > >
>  > > mv /usr/bin/rename /usr/bin/rename.orig  > > ln -s /bin/mv 
> /usr/bin/rename  >  > won't help. BackupPC doesn't use 
> /usr/bin/rename, it uses the Perl rename()  > function named after the 
> system call. Actually, /usr/bin/rename is a Perl  > script. I'm not 
> sure about the syntax, but I vaguely remember it's intended  > for 
> renaming several files, applying a Perl regexp substitution to the 
> file  > names, so you've likely just got the syntax wrong (the manual 
> page seems to  > agree with that assumption).
> 
> Not quite true...

coincidentally, the preceeding messages state something vaguely like ...

Rob Morin wrote on 2014-05-06 14:57:56 -0400 [Re: [BackupPC-users] Rename of
directories error and other   oddities...]:
RM> After a test by su to backuppc user, i created a dir named new and 
RM> then tried to rename it,  i got this error...
RM> 
RM> backuppc@locutus:~/pc/momentumvserver.momentum.local$
RM> rename /var/lib/backuppc/pc/momentumvserver.momentum.local/new
RM> /var/lib/backuppc/pc/momentumvserver.momentum.local/0
RM> 
RM> Having no space between pattern and following word is deprecated at 
RM> (eval 1) line 1.
RM> Bareword found where operator expected at (eval 1) line 1, near
"/var/lib"
RM>         (Missing operator before b?) Search pattern not terminated 
RM> at (eval 1) line 1.

I tend to believe that you'll agree that this is a Perl error message. I
would further assume that I'd get such an error message if I tried to use
something like "/var/lib/backuppc/pc/momentumvserver.momentum.local/new" as
a regular expression (because the "/var/" part is one, it's just not
supposed to be followed by "lib" without intervening space (not that the
space would help much, of course ;-)).

> [...]
> On debian systems, 'rename' is indeed a perl script calling the perl 
> rename function. Interestingly, usr/bin/rename is a link to 
> /etc/alternatives/rename which in turn is a link to /usr/bin/prename 
> (where presumably the 'p' stands for Perl)
> 
> On Fedora/Centos/Cygwin, 'rename' is a (standard) linux binary utility 
> in the standard util-linux (Linux utility) package.
> 
> The usage (unfortunately) is *not* the same... which is a pita since I 
> have needed to modify my scripts depending on what linux distro they 
> are running on...

I agree on the Debian part, believe you about the Fedora/Centos/Cygwin part
and wonder about your script part (though I see that calling a command
rather than the syscall might make sense, e.g. if you need to move cross
device or recursively, but why not use 'mv' then?), but it's really beside
the point.
BackupPC uses the syscall, not the command, unless I missed something. Thus,
replacing the command will not change anything, whether you might be on
Debian, Fedora, Centos or even Cygwin (though I doubt you'll have much fun
running the BackupPC server there).

Regards,
Holger

----------------------------------------------------------------------------
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity &#149; Requirements
for releasing software faster &#149; Expert tips and advice for migrating
your SCM now http://p.sf.net/sfu/perforce
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/