in reply to Re: Need help with mysql dump script
in thread Need help with mysql dump script

At your command prompt, type: perldoc -f chdir. It will lead you to inspect $!:
die $! unless chdir $backup_weekly_subdir;

Replies are listed 'Best First'.
Re^3: Need help with mysql dump script
by repcsi (Initiate) on Aug 18, 2011 at 14:57 UTC
    Hello, thanks, but I don't figure it out from this one:
    $ perldoc -f chdir chdir EXPR chdir FILEHANDLE chdir DIRHANDLE chdir Changes the working directory to EXPR, if possible. If +EXPR is omitted, changes to the directory specified by $ENV{HOM +E}, if set; if not, changes to the directory specified by $ENV{LOGDIR}. (Under VMS, the variable $ENV{SYS$LOGIN} +is also checked, and used if it is set.) If neither is set, "ch +dir" does nothing. It returns true on success, false otherwi +se. See the example under "die". On systems that support fchdir(2), you may pass a fileh +andle or directory handle as argument. On systems that don't su +pport fchdir(2), passing handles raises an exception. $

    Also modifing that line, is not working, also I figured, that the file removal is not working, only I just don't get any error messages:(.

      What toolic (probably) meant was the "example under "die"" mentioned in the docu of chdir. If you do "perldoc -f die" you will see these two examples:

      die "Can't cd to spool: $!\n" unless chdir '/usr/spool/news'; chdir '/usr/spool/news' or die "Can't cd to spool: $!\n"

      The two lines are equivalent (to each other and to the line toolic posted) and show how to use chdir, specifically the use of $! to print the error message that the operating system returned.

      The error message will tell you why it couldn't chdir. But to further explore the situation add

      use Cwd; #at the start of your script ... print "We are here: ",cwd(),"\n"; #test where you are in the directory + structure #alternatively this works too, but is not as portable: print "We are here:"; system('pwd');