Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Inetd question
Date: Thu, 24 Jul 2003 20:24:37 -0600
Message-ID: <63D8F97C6315D411B078009027612DD30C27DB3F@axcs11.cos.agilent.com>
From: <xiaoqin_qiu AT agilent DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

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.
 
7) Rsh complianed about no remote directory. Then I changed my home directory from a network mapped drive to local drive in /etc/passwd. 
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?

Thanks,

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

 
-----Original Message-----
From: QIU,XIAOQIN (A-Sonoma,ex1) 
Sent: Thursday, July 24, 2003 2:46 PM
To: 'cygwin AT cygwin DOT 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 AT agilent DOT com
  

 
-----Original Message-----
From: Bowden, Todd [mailto:todd DOT bowden AT atosorigin DOT com]
Sent: Thursday, July 24, 2003 1:59 PM
To: QIU,XIAOQIN (A-Sonoma,ex1); 'cygwin AT cygwin DOT 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 DOT Bowden AT atosorigin DOT com 


-----Original Message----- 
From: xiaoqin_qiu AT agilent DOT com [ mailto:xiaoqin_qiu AT agilent DOT com] 
Sent: Thursday, July 24, 2003 3:50 PM 
To: cygwin AT cygwin DOT 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 AT agilent DOT com 
  

-----Original Message----- 
From: Rob [ mailto:rob2 AT siklos DOT ca] 
Sent: Thursday, July 24, 2003 1:10 PM 
To: xiaoqin_qiu AT agilent DOT com; cygwin AT cygwin DOT 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 

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