So, that worked, but before I commit to that permanently...
What exactly do those options do? It would seem to me that now all Audits/Snapshots/BLPackages will follow sym links as well as the Config Manager. Does that mean that I could potentially be snapshotting NAS stores? Though that looks like it could be controlled by setting SnpAudPkgNetworkMounts back to no. The symbolic links I need to follow are local disk -> local disk. Is that what the CrossMounts option controls?
Look in the BladeLogicAdministration.pdf ~ p51 - there's a description in there.
I think you want to not cross network mount points, but you do want to cross the other (local) mount points.
Bounced the server, but when I go to look at a symbolic link file
I get an error. See attached screenshot.
I want to be able to audit the hosts file not as type
"Configuration" but as type "File" from the Live File System listing.
/: ls -l /etc/hosts
lrwxrwxrwx 1 root root 12 Sep 15 2009 /etc/hosts -> ./inet/hosts
i get the same message. if it's a directory, clicking on the symlink follows it. apparently not for a file. not sure if this is by design or a defect.
Did you ever get the auditing of your symbolic links working?
/etc/hosts -> ./inet/hosts
We are trying to do the same thing. Ideally we want to use compliance rules, but the fact /etc/hosts is a link does not get picked up.
The results of the rule below come back as false.
File /etc/hosts Must Exist AND (Symbolic Link = True)
Even when I try to snapshot the file from the Servers workspace the Symbolic Link property comes back as false.
No I didn't . I was told that this was the design of BL . I ended up creating
a separate audit job to check the destination file ( /etc/inet/hosts ) against
a snapshot. Maybe if enough of of ask, we can get a hotfix to change this.