On Wednesday 19 January 2005 02:28 pm, Michael W Cocke wrote:
See, I generally write this stuff for myself and then release it if I think anyone else can use it, and emails/bug reports received tell me what I need to look at in my free time. Your previous message was the first bug report I've ever received about daromizer. Difficult to believe, I know. 8-)> If I don't know anyone is using the software and it works for me, then there'll never be an update.
We did converse at length when I first started using daromizer.... (July of last year). You answered some questions but I didn't have any bugs at the time. You said you wrote it for yourself so I didn't bother you with the problems... :-) One 'feechur' that I asked about back then and I finally implemented myself is to all all of the options to be placed into an options file. This wasn't all that tough to do an it eliminates editing the daromizer script to make minor changes. Also makes things easier to deal with than trying to put them all on one line. In looking at my copy of daromizer, I see the only things unique to the script file are: 1) Directory where the slices are written (my $place = ) 2) DAR basename The above never change in my scheme of backups. Here's my DAR command line in the script: my $darcmd = 'dar -B '.$place.'daropts 2>./dar.log >>'.$place.'dar.log &'; The options file would be a nice addition.... (huh? huh? pretty pleez?) :-)