|
#1
|
|||
|
|||
Problems with Subversion script
Ever since the latest update to SD! I've been having problems getting my subversion backup scripts to run. Both worked fine before the update, and now neither works. I've even tried a different set of shell scripts, but to no avail.
=== BEGIN SCRIPT === #!/usr/bin/perl -w # # Perform a weekly backup of a Subversion repository, # logging the most-recently-backed-up revision so an # incremental script can be run other days. $svn_repos = "/path/to/svn"; $backups_dir = "/path/to/svn-backup"; $next_backup_file = "weekly-full-backup." . `date +%Y%m%d`; $youngest = `/usr/local/bin/svnlook youngest $svn_repos`; chomp $youngest; print "Backing up to revision $youngest\n"; `/usr/local/bin/svnadmin dump $svn_repos > $backups_dir/$next_backup_file`; print "Compressing dump file...\n"; print `gzip -9 $backups_dir/$next_backup_file`; open(LOG, ">$backups_dir/last_backed_up"); print LOG $youngest; close LOG; === END SCRIPT === The script works from the command line if I'm authenticated as root, but I can't seem to get it to work under SD! I've got the script set to execute (permissions of -rws--x--x), I've tried setting the SUID to both me and to the root, and every time SD! will fail with an error "Error | * Dumped revision 0." Because the error message isn't very descriptive I can only guess at what it means, but I've spent far too many hours now trying to sort it out on my own. Can anyone help, or at least point me in a new direction? |
#2
|
||||
|
||||
We haven't changed the way these scripts are executing -- we're simply calling it... I have no idea why it wouldn't work.
(You would be running authenticated; you're sure that the SVN configuration can be read in the dump line?)
__________________
--Dave Nanian |
#3
|
|||
|
|||
I'm sure that the SVN configuration can be read in the dump line. If I sudo run the same script from within the terminal the SVN dump works just fine. If I don't sudo before running the script, the dump fails. Honestly what seems to me to be happening is that SD! isn't running as authenticated (like it should) ... the script seems to fail in the same place in SD! as it does when I'm not running as a super user.
|
#4
|
||||
|
||||
It's running authenticated. Try touching a root-owned file to see.
__________________
--Dave Nanian |
#5
|
|||
|
|||
Hmmm, that works OK. I'm still completely stumped. When SD! is authenticated it works as the root user, right? What group is it part of? Wheel? Could I be running into a problem if my script is a part of the wrong group?
|
#6
|
||||
|
||||
We're running with straight-up authentication -- basically, like sudo. You won't want to re-suid your script, but I don't think it'll necessarily hurt... I think you might be making assumptions about what home folder you'll get that might mess things up.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Booting from backup | guruuno | General | 27 | 10-16-2009 11:53 PM |
Do shell script erroring? | Budgie | General | 1 | 02-08-2006 04:50 PM |
Scheduled Custom Script Uses Wrong Script? | Dasman | General | 1 | 12-08-2005 01:55 PM |
Problems backing up to LaCie 500 gb | RichardRipley | General | 3 | 11-30-2005 06:12 PM |
Error: No space left on device | tradervic | General | 11 | 06-29-2005 04:50 PM |