From: Chris Abbey <cabbey@bresnanlink.net>
To: <cygwin@sourceware.cygnus.com>
Subject: Re: mount points and inetd
Date: Sun, 17 Sep 2000 01:06:00 -0000 [thread overview]
Message-ID: <4.3.2.7.0.20000917015958.00bda100@pop.bresnanlink.net> (raw)
In-Reply-To: <003701c02074$f46a8290$f7c723cb@lifelesswks>
At 18:00 9/17/00 +1100, Robert Collins wrote:
>Two thoughts:
>
>are your mounts system or user mounts?
all user as I showed, but I think the three created by default
*should* be system; at least / should be.... I've just moved them
over to system mounts and am rebooting now...
ok, that fixes the three important ones, but that exposes me to
the userid behavior... I guess I'll just make *all* my mounts
system mounts (in which case I'll question the usefulness of
having user mode mounts at all.)
>two: inetd may be trying to start before the networking services have
>started: ie before tcp is available.
hmmm... good idea, although I should have pointed out that the
failure was clearly mount point related as the logs showed that
it couldn't find /etc/inetd.conf
actually... shouldn't inetd --install-as-service do this
automatically? I've created the reg key myself for this,
just to prevent future wierdness though. ;) If anyone wants
directions on how to do this let me know.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-09-17 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-16 23:56 Chris Abbey
2000-09-16 23:59 ` Robert Collins
2000-09-17 1:06 ` Chris Abbey [this message]
2000-09-17 1:13 ` Robert Collins
2000-09-17 1:41 ` Chris Abbey
2000-09-18 13:11 ` DJ Delorie
2000-09-18 13:10 ` DJ Delorie
2000-09-18 21:11 ` Chris Abbey
2000-09-19 0:37 ` Andrej Borsenkow
2000-09-19 6:42 ` Jason Tishler
2000-09-19 7:17 ` DJ Delorie
2000-09-19 11:50 ` [PATCH]: setup.exe defaults install scope (was Re: mount points and inetd) Jason Tishler
2000-09-19 14:18 ` mount points and inetd Corinna Vinschen
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=4.3.2.7.0.20000917015958.00bda100@pop.bresnanlink.net \
--to=cabbey@bresnanlink.net \
--cc=cygwin@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).