I've not sure exactly, I guess they are required to be there for some hard coded paths. I see after installation some components (client, bridge, lib etc.) are symlinked in /usr/share/cloud/management.
Regards. ________________________________________ From: David Nalley [da...@gnsa.us] Sent: Monday, October 08, 2012 11:24 PM To: cloudstack-dev@incubator.apache.org Subject: Re: git commit: CLOUDSTACK-221: Force symlink if any existing symlink On Mon, Oct 8, 2012 at 1:46 PM, Rohit Yadav <rohit.ya...@citrix.com> wrote: > This is just to enforce a symlink. For example, when I install and remove > CloudStack for the first time, the symlink will be created and will point to > a location which does not exist (as I removed it). > Then, when I try to install again, it will simply give a warning. By doing ln > -sf, we enforce symlink just in case there is an existing symlink it would > set it to correct path. > The other change, -h instead of -e (in if conditional) is to check for > symlink existence. > > Regards. I understand what enforcing a symlink means - my question was more general (your commit just touched that swath of code, so not really asking why you moved to enforcing that symlink) Why is there a symlink there in the first place. It seems like a hack
