Glad that you have no issue anymore, even thou we don't really know what
the reason was :-/
I have to beg your pardon, but I have no extra experience with large
disk access mdoe other than seeing a few forum/blog entries referring to
it - there were no related bugs nor a lot of official
I tried a bit with this script but I never got any Data into the Log
File.
Now I did a Ubuntu Reinstallation. Now every thing worked and Ubuntu is
Booting way faster.
Maybe out of topic:
If I boot into VMWARE Bios there is a "Large Disk Access Mode" This is set to
DOS. Some Article in Internet
maybe tmp is cleaned afterwards?
I didn't check yet when vmware is calling these.
since this is only sh (dash in this case I'd think) it didn't like all the
syntax.
The following worked for me in a quick test:
set -x
LOG_FILE=/var/log/vmware-nethook-both.log
exec >>${LOG_FILE}
exec
I added
LOG_FILE=/tmp/both.log
exec > >(tee -a ${LOG_FILE} )
exec 2> >(tee -a ${LOG_FILE} >&2)
in the head of /etc/vmware-tools/scripts/vmware/network
but I do not get any log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Odd, even the poweron-vm that fails on boot works in this retest.
If there is only /etc/vmware-tools/scripts/vmware/network and no others
as it usually is we might then need to find what happens on boot to fail
there.
I wonder if you could try to modify /etc/vmware-tools/scripts/vmware/network
excec bit is set.
---
bash -x /etc/vmware-tools/scripts/vmware/network poweron-vm; echo $?
--
++ date
+ echo Fre Jan 5 14:37:15 CET 2018 ': Executing
'\''/etc/vmware-tools/scripts/vmware/network'\'''
Fre Jan 5 14:37:15 CET 2018 : Executing
Hi Adler,
I lack an env to repro but looking through search engines I think you want to
check what the guest has in:
$ find /etc/vmware-tools/scripts
Check if the files there have the exec bit set (and add it if not) - I
found reports of those being lost triggering the issue.
You likely have
