Marcelo, Quoting Marcelo Vanzin <[email protected]>: > On 12/17/2011 08:53 AM, Heiko Zuerker wrote: >> Exit status is 1. >> It's complaining that the ifup script is not found by the network script. >> I see the network script is also looking for "ifconfig", which we do not >> include anymore (we transistioned to "ip"). >> >> It seems I'll have to create a custom network script, or disable that >> functionality completely. > > That seems to be the easiest course for you. Out of curiosity, what > distro are > you using?
I'm the maintainer of Devil-Linux. I'm working on the next release, that's when I came across the problem. >> What I don't understand is why does it shut down when I try it the 2nd time? > > It's a feature for cases when the scripts are broken. In WS / > Fusion, you would > have seen a dialog box saying something like "running scripts > failed, try again > to force shutdown". On ESX I believe the message would have shown up > in the VM's > event log, viewable from the vSphere client UI. Ah okay, that makes sense. The script didn't seem to do anything which would be important for my distro, that's why I decided to remove it. If I understood it right, it's mostly does things for pausing and restoring VM's, is that correct? -- Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ open-vm-tools-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
