I keep getting complaints that vmware and cups form a dependency cycle,
although I haven't seen it be a problem in practice.
However, I just rebooted my system (a very rare event), and found that there's
a real problem with vmware and apache2. Apache2 comes first, but it's set
up knowing about the pseudo-networks that vmware establishes, and it's
starting before the networks are alive. This makes it give up and die.
Summary:
-- is there actually a problem between cups and vmware, and if that's
"maybe", how can I tell for sure.
-- how do I adjust the order of scripts so that apache starts after vmware?
--
Kevin O'Gorman, PhD
--
[email protected] mailing list
