public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] VMware and the order of init scripts
Date: Sat, 16 Sep 2006 09:57:44 -0700	[thread overview]
Message-ID: <9acccfe50609160957l17151be1je2d593d4af9d3b09@mail.gmail.com> (raw)

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
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-09-16 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-16 16:57 Kevin O'Gorman [this message]
2006-09-16 18:50 ` [gentoo-user] VMware and the order of init scripts Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9acccfe50609160957l17151be1je2d593d4af9d3b09@mail.gmail.com \
    --to=kogorman@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox