Date: Thu, 04 Jun 2015 14:59:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 200637] sysutils/open-vm-tools: vmrun guest commands do not work [FIX] Message-ID: <bug-200637-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200637 Bug ID: 200637 Summary: sysutils/open-vm-tools: vmrun guest commands do not work [FIX] Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: bms@fastmail.net In FreeBSD, the following vmrun commands fail to operate due to a PAM-related permissions issue: copyFileFromHostToGuest, runProgramInGuest, runScriptInGuest. Symptom: If I try to use vmrun with e.g. a passwordless account, I get the following log message: %%% Nov 27 16:49:11 myhost vmsvc[9911]: in openpam_load_module(): no pam_unix2.so found %%% Root cause: The PAM configuration installed with the port refers to non-existent PAM modules. Resolution: Remove the non-existent PAM modules from the configuration installed for vmtoolsd. %%% sed -i.orig -e '/pam_unix2/d;/pam_unix_auth/d;/pam_unix_acct/d' /usr/local/etc/pam.d/vmtoolsd %%% With this change, vmrun commands will work with the following caveats at the host: - The runScriptInGuest command takes the content -- not a path -- of a script to be executed with /bin/sh. - vmrun logs error messages to stdout, so they need to be parsed for guest command return codes. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200637-13>