Inetd question

xiaoqin_qiu@agilent.com xiaoqin_qiu@agilent.com
Fri Jul 25 23:04:00 GMT 2003


Hi Igor and Larry,

Thank you very much for your information.

For rsh, I can use hosts.equiv instead of .rhosts on FAT32 drive. That is a acceptable solution for me.

Just FYI, the cygwin package I installed was 1.3.22-1 not 1.5.0 and the .dll was 1.3.22. After I upgraded login package, I just reinstalled the same cygwin package. I verified this by running cygcheck -s. 

The interesting thing is now cygcheck -s showed login package is 1.9.5 not 1.9.6 although I am pretty sure I upgraded login package from 1.9.5 (installed by default) to 1.9.6. Maybe the reinstall of cygwin package changed it somehow? If the only difference between 1.9.6 and 1.9.5 is compiling for different cygwin version. I shouldn't need to use 1.9.6 because I am running cygwin 1.3.22. I may try the installation again.

Thanks,

Xiaoqin Qiu
Technical Computing Group
IT Infrastructure Services Organization
Agilent Technologies, Inc.
(818)879-6220
xiaoqin_qiu@agilent.com
 

-----Original Message-----
From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
Sent: Thursday, July 24, 2003 7:41 PM
To: QIU,XIAOQIN (A-Sonoma,ex1)
Cc: cygwin@cygwin.com
Subject: RE: Inetd question


On Thu, 24 Jul 2003 xiaoqin_qiu@agilent.com wrote:

> Hi,
>
> Telnet is working now, rsh is working half-way. Here is what I did:
>
> 1) I uninstalled everything.
> 2) I reinstalled cygwin with default packages.
> 3) Then I installed inetd package, ran iu-config, mkpasswd,... However,
>    it still didn't work.
> 4) Then I upgraded login package to the latest 1.9.6 from 1.9.5.
> 5) Then reinstalled cygwin package again because before the
>    reinstallation of cygwin package, login.exe got "The procedure entry
>    point _getreent could not be located in the dynamic link library
>    cygwin1.dll." error.
> 5) Changed my UID in /etc/passwd to one less than 65536, otherwise, I
>    got couldn't switch to my account error in telnet login session.
> 6) Telnet worked.

FYI, login has nothing to do with this (or, at least, not directly).  You
must've hit a bug that was fixed in Cygwin 1.5.0, and installing that made
telnet work.  The only difference between login 1.9-6 and 1.9-5, IIRC, is
that 1.9-6 is compiled for Cygwin 1.5.0, hence the need to update Cygwin.

The second step 5) above is weird, though (not just because there are two
5's), since Cygwin 1.5.0 is supposed to have 32-bit UIDs...

> 7) Rsh complianed about no remote directory. Then I changed my home
>    directory from a network mapped drive to local drive in /etc/passwd.

This would happen, since you use passwordless authentication, and network
shares usually aren't available in that mode.

> 8) Rsh still complained Permission denied. Then I setup /etc/hosts.equiv
>    and rsh worked. But .rhosts is still not working.
>  My .rhosts file in on a FAT32 file system. In the bash window, I ran ls
> -l .rhosts, it showed 644. However, when I ran rsh, Windows event log
> showed bad .rhosts owner. This file is owned by my account. Inetd is
> starting with local admin account. And I tried to chown SYSTEM .rhosts.
> It didn't work. I have CYGWIN=ntsec. Maybe it is related to FAT32?

Yes.  FAT filesystems don't store permissions at all.  Cygwin has an
"ntea" mode that should also store ownership (if that patch was ever
applied -- I'm too lazy to go look right now), but it won't work for
FAT32.  Sorry.  Either use an NTFS filesystem, or use FAT and add "ntea"
to your CYGWIN variable.
	Igor

> Thanks,
> Xiaoqin Qiu
>
>
> -----Original Message-----
> From: QIU,XIAOQIN (A-Sonoma,ex1)
> Sent: Thursday, July 24, 2003 2:46 PM
> To: 'cygwin@cygwin.com'
> Subject: RE: Inetd question
>
>
> Todd is right. I used this syntax and I could get my account passwd
> entry quickly. However, when I tried to do the same thing for mkgroup -d
> -u <uname> <domain name>, I got error "Cannot get PDC, code = 2453"
> after it printed SYSTEM group entry.
>
>  And I am quite concern about why when I started inetd using local admin
> user, the inetd process running using UID 400 and I got connection
> refused error.
>
> Any idea?
>
> Xiaoqin Qiu
> Technical Computing Group
> IT Infrastructure Services Organization
> Agilent Technologies, Inc.
> (818)879-6220
> xiaoqin_qiu@agilent.com
>
>
> -----Original Message-----
> From: Bowden, Todd [mailto:todd.bowden at atosorigin dot com]
> Sent: Thursday, July 24, 2003 1:59 PM
> To: QIU,XIAOQIN (A-Sonoma,ex1); 'cygwin@cygwin.com'
> Subject: RE: Inetd question
>
> Acutally the command would be the following:
>
> mkpasswd -d -u <username> <DOMAINNAME> >> /etc/passwd
>
> This would not get everyone in your domain.
>
> Todd C. Bowden
> HP Certified
> AtosOrigin
> 5000 S. Bowen
> Arlington, TX 76017
> Office: 817-264-8211
> E-mail: Todd.Bowden@atosorigin.com
>
>
> -----Original Message-----
> From: xiaoqin_qiu@agilent.com [ mailto:xiaoqin_qiu@agilent.com]
> Sent: Thursday, July 24, 2003 3:50 PM
> To: cygwin@cygwin.com
> Subject: RE: Inetd question
>
>
> I tried that. But it still took long time and had a lot of other
> people's entries showing up. Thanks,
>
> Xiaoqin Qiu
> Technical Computing Group
> IT Infrastructure Services Organization
> Agilent Technologies, Inc.
> (818)879-6220
> xiaoqin_qiu@agilent.com
>
>
> -----Original Message-----
> From: Rob [ mailto:rob2@siklos.ca]
> Sent: Thursday, July 24, 2003 1:10 PM
> To: xiaoqin_qiu@agilent.com; cygwin@cygwin.com
> Subject: Re: Inetd question
>
>
> > 2)  I didn't run mkpasswd -d because the domain is too big that it is
> > going to take forever.
>
> you could run: mkpasswd -d -u myusername >> /etc/passwd

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


--
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/



More information about the Cygwin mailing list