Thanks, just to be precise - in systemimager 3.8.1
- I had to comment OUT the line containing /var/lib/nfs/* in the
/usr/sbin/si_getimage file.
Regards,
Marcin
Andrea Righi wrote:
Marcin Dulak wrote:
Hi,
systemimager (version 3.8.1, *.noarch.rpm from sourceforge) installed on
CentOS5 (uses nfs-utils-1.0.9-16.el5),
excludes automatically /var/lib/nfs/* from the image, which results in
the following error when service nfslock start
on a node cloned using this image:
Starting NFS statd: statd: Could not chdir: No such file or directory
[FAILED]
What is the correct way of handling /var/lib/nfs/* with systemimager on
CentOS5?
You could use the file /etc/systemimager/getimage.exclude, uncommenting the
/var/lib/nfs/* entry, but this file has been introduced in 3.9.0. I think we
should backport the patch, so that it'll be available in the next stable
release.
An ugly workaround in 3.8.1 is to uncomment it directly in
/usr/sbin/si_getimage.
-Andrea
-
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-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
-
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-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
