Nataraj wrote:
I would check for a selinux violation in /var/log/audit/audit.log and/or /var/log/messages. You can temporarily try "setenforce 0" to test and then update the selinux policy afterwards. I've seen this problem under CentOS 5.2 with Vmware server 2. I've also seen other problems where the hostd and/or the webaccess process would not run for other reasons.
Good suggestions, but audit.log only appears to contain messages for vmware-hostd which are after I disabled SELinux. messages also did not contain anything which would indicate that SELinux was involved. -- Michael Eager eager@xxxxxxxxxxxx 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077 -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
