On Mon, Mar 7, 2011 at 3:24 AM, Ole Pinto <olepi...@gmail.com> wrote:
> As you are scheduling your job to run with your user, I don't think it is a
> permissions related problem. But maybe the env. vars do matter, including
> any needed to get to your stored password.
>
> Once you get to stderr you'll probably have a clue about what is happening.
> If not, from your perl script print the environment vars, and reproduce that
> in an interactive shell. If it doesn't work, there you have it. Now you
> would only need to compare this to a "normal" shell, and make small
> modifications until you make it work.
>
> On Sun, Mar 6, 2011 at 20:45, bimininavels <c...@qgenuity.com> wrote:
>>
>> I've been struggling all morning with what should be a very simple
>> problem.
>>
>> I would like to commit and update a svn repository daily using cron. I've
>> encapsulated my svn calls into a perl script, which runs the following
>>
>> ----
>> #!/usr/bin/perl
>>
>> print "To run svn commit\n";
>> $thetime=time;
>>
>> system "cd ~/docs; /usr/bin/svn commit --message '$thetime' \n";
>> system "cd ~/docs; /usr/bin/svn info \n";
Hello. Is that "$thetime" getting parsed?
Look, for 3 lines of code, you don't need perl.
#!/bin/sh
cd ~/docs || exit 1
/usr/bin/svn commit --message "`date`"
/usr/bin/svn info
Done. Note the exit if the "cd" fails, and set whatever "date" format you want.
