In the below, I made a reference to $overrides. This should have been
$default_override_dir. The variable for $default_override_dir is not in
Server.pm and perhaps should be yanked in with the same method that
si_getimage uses as per below:
my $default_override_dir = $config->default_override_dir();
-Dustin Kamper
On 8/22/07, Dustin Kamper <[EMAIL PROTECTED]> wrote:
>
>
> I changed my configuration in /etc/systemimager/systemimager.conf so the
> path '/var/lib/systemimager' is now /systemimager. Had to do this because
> of the layout of the server I am using to store images and I would prefer
> not to hide the images directory in an obscure location.
>
> When I run si_getimage, everything seems to works OK and the data is saved
> to /systemimager/images as expected. When si_getimage runs through the auto
> install script configuration section, I get the following error:
>
> FATAL: Can't make directory /var/lib/systemimager/overrides/<image name>
> (Note: I expected this to be looking for /systemimager/overrides as
> defined in /etc/systemimager/systemimager.conf)
>
>
> I traced this down to /usr/lib/systemimager/perl/SystemImager/System.pm
> line 1938 (SI 3.8.1):
>
> my $dir = "/var/lib/systemimager/overrides/$script_name";
> if (! -d "$dir") {
> mkdir("$dir", 0755) or die "FATAL: Can't make directory $dir\n";
> }
>
>
> Shouldn't this be using the variable $overrides instead? Not sure what
> this would affect negatively if I just change it though...I have not
> investigated any more than this.
>
>
>
> -Dustin Kamper
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
