more on inetd problems

[Jim.George]

On Thu, 27 Jun 2002, Christopher Faylor wrote:

> On Thu, Jun 27, 2002 at 08:46:09PM +0100, Jim.George wrote:
> >On Thu, 27 Jun 2002, Corinna Vinschen wrote:
> >
> >> On Wed, Jun 26, 2002 at 09:18:16PM +0100, Jim.George wrote:
> >> > > So, is the DLL on the path? executable by this user? etc.
> >> >
> >> >   I've tried putting the DLL at the start of my path, in the middle, and
> >> > at the end but to no avail.
> >>
> >> ...and executable by everyone?
> >>
> >> Corinna
> >Yes they are all executable by everyone.
> >
> >When I say all I have cygwin1.dll in the following directories
> >
> >	/bin, /usr/sbin, /usr/bin, /usr/local/bin, /usr/local/sbin
> >
<snip>
>
> Are you saying that you have multiple copies of the Cygwin DLL on your
> system?  If so, only the one in /bin (aka /usr/bin) is the right one.
> You should *NOT* have more than one cygwin DLL on your system.
>
> You also should *NOT* put the cygwin DLL in some "system" directory.
> Just modify your environment (via Control Panel) to include c:\cygwin\bin
> (or whatever) in your system PATH.
>
Chris,

	I removed all cygwin1.dlls except the one in /bin.  I ensured that my
Control Panel PATH had E:\cygwin\bin at the start.

	I then tried to restart inetd and got an error stating that no
cygwin1.dll could be found in a path that I have no recollection of.  It
starts with e:\cygwin\usr\bin and then has multiple entries for windows system
directory (I hasten to add that they all point to the same directory and none
of them contain cygwin1.dll).

	So I tried creating a symlink from /bin to /usr/local/bin but although
this started the inetd service I still get the original problem...bash failed
to initialise properly.

	Can you tell me where this crazy path might have come from?

Thanks,

Jim



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/