This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: problems with cygrunsrv and inetd
Actually, the inetd README mentions this as part of it's history:
- No user mount point is valid anymore! You have to install all
your mount points in the system mount table. This doesn't
change after you have logged in to a normal user account eg.
via telnet/rlogin. It's possible that we can use the user
mounts as soon as somebody contributes a patch to login and
ftp that allows loading a user hive into the registry after
authentication.
In general, this has been discussed on this list and hasn't been propagated
to various READMEs, the user guide, or other docs. Feel free to offer a
patch where you feel it's appropriate.
Larry
At 01:07 PM 1/12/2004, Ruud Huynen you wrote:
>Hello Larry
>
>Thank you for your explanation, which points directly to the problem.
>I did a lot of reading yesterday, internet, faqs, userguide, readme files.
>I didn't find anything pointing into this direction.
>The problem occurs in inetutils and sshd and maybe other packages.
>I think it should be described in the readme's and in the userguide.
>
>Ruud
>
>----- Original Message -----
>From: "Larry Hall" <cygwin-lh@cygwin.com>
>To: "Ruud Huynen" <ruud.huynen@hispeed.ch>; "Cygwin List"
><cygwin@cygwin.com>
>Sent: Sunday, January 11, 2004 9:28 PM
>Subject: Re: problems with cygrunsrv and inetd
>
>
>> Actually, yes. Installing for "Just me" creates mount points only for the
>> current user. All services started by Cygwin are, by default, started as
>> another user, typically SYSTEM, which won't see the user-specific mount
>> points. To run services "right out of the box" with Cygwin, you really
>> need to install for "All Users". Looking back now at your report, I guess
>> there was the hint of this issue in the report and your cygcheck output
>> clearly shows user mounts. Sorry I didn't pick up on this and point it
>out
>> to you sooner. The alternative to reinstalling everything would have been
>> to just remount all your mounts as 'system' rather than 'user' (see 'man
>> mount') or rerunning setup again without uninstalling and picking "All
>> users" insteaad. But you clearly got to where you want to be with your
>> method. Good catch on your part! Glad you got it working.
>>
>> Larry
>>
>>
>> At 03:17 PM 1/11/2004, Ruud Huynen you wrote:
>> >Hello
>> >
>> >I reinstalled cygwin completely and it works now. Inetd and ssh are
>working
>> >in 2 minutes.
>> >This time I used the setup setting Install For 'All Users'.
>> >
>> >Is there a problem with installing inetd and sshd when using 'Just me' ?
>> >
>> >Regards
>> >Ruud
>> >----- Original Message -----
>> >From: "Larry Hall" <cygwin-lh@cygwin.com>
>> >To: "Ruud Huynen" <ruud.huynen@hispeed.ch>; <cygwin@cygwin.com>
>> >Sent: Sunday, January 11, 2004 8:02 PM
>> >Subject: Re: problems with cygrunsrv and inetd
>> >
>> >
>> >> At 12:32 PM 1/11/2004, Ruud Huynen you wrote:
>> >> >Hello
>> >> >
>> >> >I looked on the internet and inetutils.README to install the inetd and
>> >the
>> >> >ssh service.
>> >> >When I create the windows service inetd with:
>> >> >cygrunsrv -I inetd -d "CYGWIN inetd" -p /usr/sbin/inetd -a -d -e
>> >> >CYGWIN=ntsec
>> >>
>> >>
>> >> Why did you install it this way? inetutils.README clearly states that
>> >> the inetd service is installed with the '--install-as-service' flag.
>> >>
>> >>
>> >> >I noticed that the executable pointed to in the service is, which is
>> >wrong:
>> >> >C:\cygwin\bin\cygrunsrv.exe
>> >>
>> >>
>> >> No, it's not wrong for a service installed with cygrunsrv.
>> >>
>> >>
>> >> >After removing it
>> >> >cygrunsrv -R inetd
>> >> >
>> >> >And using:
>> >> >/usr/sbin/inetd.exe --install-as-service
>> >> >I have in the service: C:\cygwin\usr\sbin\inetd.exe
>> >> >
>> >> >Starting it shows the two inetd processes running, but netstat -an
>does
>> >not
>> >> >show any listening ports!
>> >>
>> >>
>> >>
>> >> From inetutil.README:
>> >>
>> >> Current caveat: inetd is visible twice in the process list.
>> >> This is currently needed to work correctly with the service
>> >> manager. This should be solved in a future release.
>> >>
>> >>
>> >> >I thought -d means debugging. Not daemon. But I tried it and changed
>the
>> >> >registry to add the -d. The same behaviour is noticed.
>> >> >
>> >> >Only by using the following command I have the ports open, and can
>> >connect:
>> >> >$ /usr/sbin/inetd.exe -d &
>> >> >[1] 2936
>> >> >
>> >> >Ruud@pc11 /
>> >> >$ ADD : echo proto=tcp, wait=0, user=root builtin=4080d0
>server=internal
>> >> >registered internal on 4
>> >> >ADD : echo proto=udp, wait=0, user=root builtin=4080e0 server=internal
>> >> >registered internal on 5
>> >> >ADD : discard proto=tcp, wait=0, user=root builtin=4080f0
>server=internal
>> >> >registered internal on 6
>> >> >ADD : discard proto=udp, wait=0, user=root builtin=408100
>server=internal
>> >> >registered internal on 7
>> >> >ADD : daytime proto=tcp, wait=0, user=root builtin=408130
>server=internal
>> >> >registered internal on 8
>> >> >ADD : daytime proto=udp, wait=0, user=root builtin=408140
>server=internal
>> >> >registered internal on 9
>> >> >ADD : chargen proto=tcp, wait=0, user=root builtin=408150
>server=internal
>> >> >registered internal on 10
>> >> >ADD : chargen proto=udp, wait=0, user=root builtin=408160
>server=internal
>> >> >registered internal on 11
>> >> >ADD : time proto=tcp, wait=0, user=root builtin=408110 server=internal
>> >> >registered internal on 12
>> >> >ADD : time proto=udp, wait=0, user=root builtin=408120 server=internal
>> >> >registered internal on 13
>> >> >ADD : ftp proto=tcp, wait=0, user=root builtin=0
>server=/usr/sbin/in.ftpd
>> >> >registered /usr/sbin/in.ftpd on 14
>> >> >ADD : telnet proto=tcp, wait=0, user=root builtin=0
>> >> >server=/usr/sbin/in.telnetd
>> >> >registered /usr/sbin/in.telnetd on 15
>> >> >ADD : shell proto=tcp, wait=0, user=root builtin=0
>> >server=/usr/sbin/in.rshd
>> >> >registered /usr/sbin/in.rshd on 16
>> >> >ADD : login proto=tcp, wait=0, user=root builtin=0
>> >> >server=/usr/sbin/in.rlogind
>> >> >registered /usr/sbin/in.rlogind on 17
>> >> >ADD : exec proto=tcp, wait=0, user=root builtin=0
>> >server=/usr/sbin/in.rexecd
>> >> >registered /usr/sbin/in.rexecd on 18/usr/bin/ssh-host-config -y
>> >> >ADD : talk proto=udp, wait=1, user=root builtin=0
>> >server=/usr/sbin/in.talkd
>> >> >registered /usr/sbin/in.talkd on 19
>> >> >ADD : ntalk proto=udp, wait=1, user=root builtin=0
>> >server=/usr/sbin/in.talkd
>> >> >registered /usr/sbin/in.talkd on 20
>> >> >
>> >> >Using /usr/sbin/inetd.exe without the '-d' does not work.
>> >>
>> >>
>> >> Sounds to me like you didn't run iu-config. I'd recommend
>uninstalling,
>> >> removing /etc/inetd.conf, reinstalling, and running iu-config.
>> >>
>> >>
>> >> >Using the "/usr/bin/ssh-host-config -y" to configure ssh has the same
>> >> >problem. In the service the executable is
>'C:\cygwin\bin\cygrunsrv.exe'.
>> >> >
>> >> >What is wrong ?
>> >>
>> >>
>> >> Nothing. That's correct.
>> >>
>> >>
>> >> --
>> >> Larry Hall http://www.rfk.com
>> >> RFK Partners, Inc. (508) 893-9779 - RFK Office
>> >> 838 Washington Street (508) 893-9889 - FAX
>> >> Holliston, MA 01746
>> >>
>> >>
>> >
>> >
>> >
>> >--
>> >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>> >Problem reports: http://cygwin.com/problems.html
>> >Documentation: http://cygwin.com/docs.html
>> >FAQ: http://cygwin.com/faq/
>>
>
>
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Problem reports: http://cygwin.com/problems.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/