public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* RE: Cron Running As UID 400
@ 2004-02-25 18:13 Winch Jr., Wayne S
  2004-02-25 18:29 ` Pierre A. Humblet
  0 siblings, 1 reply; 7+ messages in thread
From: Winch Jr., Wayne S @ 2004-02-25 18:13 UTC (permalink / raw)
  To: cygwin; +Cc: Harig, Mark

Mark,

Thanks for your quick reply.  I'm sorry that I had neglected to mention
that I had already run the cron_diagnose.sh script and it reported that
no problems were found; I ran it again just now as a sanity check and
still no problems found.  I did try uninstalling/reinstalling the cron
service as suggested by cron_diagnose.sh (several times with
variations), but cron still does not kick jobs off as expected.

My test crontab is as follows:

$ crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.3604 installed on Tue Feb 24 12:15:13 2004)
# (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp
$)
0 0-23/4 * * * /usr/bin/updatedb
* * * * * pwd > /tmp/crontest 


Also, I was able to get cron running properly on my home system (Windows
XP Pro).  In that setup, I once again noticed that cron and its parent
cygrunsrv processes are identified as running under SYSTEM vice unknown
user 400 as on my office system that doesn't work.

Regards,

Wayne

-----Original Message-----
From: Harig, Mark [mailto:maharig@idirect.net] 
Sent: Wednesday, February 25, 2004 7:56 AM
To: Winch Jr., Wayne S; cygwin@cygwin.com
Subject: RE: Cron Running As UID 400

Please read the message in the Cygwin mailing list at:

http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html

It will provide you with a script that will attempt to diagnose the
problem that you are having with cron.


> -----Original Message-----
> From: Winch Jr., Wayne S [mailto:Wayne.WinchJr@ca.com]
> Sent: Tuesday, February 24, 2004 4:06 PM
> To: cygwin@cygwin.com
> Subject: Cron Running As UID 400
> 
> 
> Hi,
> 
> I've been through a couple of problems already with cron and have 
> resolved all of them (thanks to this list!) except this last one.  The

> cron service is indeed running, but no jobs are ever run as described 
> in the crontab.  A strange thing I've noted is that the user that the 
> cron service is running under is not the expected SYSTEM but the 
> unknown 400
> as:
> 
> $ ps -ef
>      UID     PID    PPID TTY     STIME COMMAND
>  winwa02     904       1   ?    Feb 23 /usr/X11R6/bin/XWin
>   SYSTEM    3912       1   ?    Feb 23 /usr/bin/cygrunsrv
>   SYSTEM    1512    3912   ?    Feb 23 /usr/sbin/inetd
>   SYSTEM    2616       1   ?    Feb 23 /usr/bin/cygrunsrv
>   SYSTEM    2648    2616   ?    Feb 23 /usr/sbin/cygserver
>  winwa02    1412       1   4    Feb 23 /usr/bin/rxvt
>  winwa02    3552    1412   5    Feb 23 /usr/bin/bash
>  winwa02    3084    3552   5    Feb 23 /usr/bin/telnet
>  winwa02    3228       1   2  14:16:18 /usr/bin/rxvt
>  winwa02    3640    3228   3  14:16:19 /usr/bin/bash
>  winwa02    3176    3640   3  15:46:35 /usr/bin/telnet
>  winwa02    3016       1   6  16:06:23 /usr/bin/rxvt
>  winwa02    2504    3016   7  16:06:23 /usr/bin/bash
>  winwa02    3856       1   0  11:13:47 /usr/bin/rxvt
>  winwa02    3576    3856   1  11:13:48 /usr/bin/bash
>      400    2228       1   ?  12:30:59 /usr/bin/cygrunsrv
>      400     536    2228   ?  12:30:59 /usr/sbin/cron
>  winwa02    2188    2504   7  12:37:47 /usr/bin/ps
> 
> 
> 
> Note that other cygrunsrv processes do indeed correctly run under 
> SYSTEM.  I suspect that if my cron and its associated parent cygrunsrv

> process were running as SYSTEM, then the cron jobs would execute per 
> the crontab.  In fact, I manually ran /usr/sbin/cron as my user 
> (winwa02) and cron was indeed able to kick off the crontab jobs 
> properly.
> 
> A relevant entry in the Windows XP Application Event log appears in 
> full when /usr/sbin/cron starts as:
> 
> The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot

> be found. The local computer may not have the necessary registry 
> information or message DLL files to display messages from a remote 
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this

> description; see Help and Support for details. The following 
> information is part of the event: /usr/sbin/cron : PID 536 : (winwa02)

> ORPHAN (no passwd entry).
> 
> The typical command line used to install the cron service was:
> 
> cygrunsrv -I cron -p /usr/sbin/cron -a -D -e "CYGWIN=tty ntsec" -d 
> "CYGWIN cron"
> 
> My domain /etc/passwd and /etc/group files are up-to-date.
> 
> As usual the output of the relevant sections of cygcheck -svr appears
> below:
> 
> 
> Cygwin Win95/NT Configuration Diagnostics Current System Time: Tue Feb

> 24 11:08:08 2004
> 
> Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
> 
> ----------snip----------
> 
> Output from C:\cygwin\bin\id.exe (nontsec)
> UID: 5120(winwa02) GID: 10513(Domain Users) 10513(Domain Users)
> 
> Output from C:\cygwin\bin\id.exe (ntsec)
> UID: 5120(winwa02) GID: 10513(Domain Users)
> 544(Administrators)           
> 545(Users)                    143344(442-SC-CRO-R)
> 106908(98-Site)               
> 10513(Domain Users)           162415(NASiteGroups)
> 169978(North American Sites)
> 
> SysDir: C:\WINDOWS\System32
> WinDir: C:\WINDOWS
> 
> CYGWIN = `tty notitle glob ntsec codepage:oem server'
> HOME = `C:\cygwin\home\winwa02'
> MAKE_MODE = `unix'
> PWD = `/home/winwa02'
> USER = `winwa02'
> 
> ----------snip----------
> 
> 
>  1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2004/1/30 16:32
>     Cygwin DLL version info:
>         DLL version: 1.5.7
>         DLL epoch: 19
>         DLL bad signal mask: 19005
>         DLL old termios: 5
>         DLL malloc env: 28
>         API major: 0
>         API minor: 109
>         Shared data: 3
>         DLL identifier: cygwin1
>         Mount registry: 2
>         Cygnus registry name: Cygnus Solutions
>         Cygwin registry name: Cygwin
>         Program options name: Program Options
>         Cygwin mount registry name: mounts v2
>         Cygdrive flags: cygdrive flags
>         Cygdrive prefix: cygdrive prefix
>         Cygdrive default prefix: 
>         Build date: Fri Jan 30 19:32:04 EST 2004
>         CVS tag: cr-0x9e
>         Shared id: cygwin1S3
> 
> ----------snip----------
> 
> Cygwin Package Information
> Last downloaded files to: C:\Documents and Settings\winwa02\My 
> Documents\My Downloads\cygwin Last downloaded files from:
ftp://mirrors.rcn.net/pub/sourceware/cygwin

Package                 Version            
---------- snip ----------
cron                    3.0.1-11           
crypt                   1.1-1              
ctags                   5.5-4              
cygipc                  2.03-2             
cygrunsrv               0.98-1             
---------- snip ----------

Use -h to see help about each section



Thanks,

Wayne Sheridan Winch, Jr.


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Cron Running As UID 400
  2004-02-25 18:13 Cron Running As UID 400 Winch Jr., Wayne S
@ 2004-02-25 18:29 ` Pierre A. Humblet
  0 siblings, 0 replies; 7+ messages in thread
From: Pierre A. Humblet @ 2004-02-25 18:29 UTC (permalink / raw)
  To: cygwin

Wayne,

The only reason why a Cygwin process runs with uid 400
is that its SID was not found in /etc/passwd when first
starting from Windows (you can observe that by temporarily
renaming /etc/passwd and starting a fresh Cygwin process).
It's stange that this happens only for one cygrunsrv process 

Please use the Windows Task Manager ("Processes" tab) and
report the User of the strange cygrunsrv, according to Windows.
 
Pierre

On Wed, Feb 25, 2004 at 12:41:20PM -0500, Winch Jr., Wayne S wrote:
> Mark,
> 
> Thanks for your quick reply.  I'm sorry that I had neglected to mention
> that I had already run the cron_diagnose.sh script and it reported that
> no problems were found; I ran it again just now as a sanity check and
> still no problems found.  I did try uninstalling/reinstalling the cron
> service as suggested by cron_diagnose.sh (several times with
> variations), but cron still does not kick jobs off as expected.
> 
> My test crontab is as follows:
> 
> $ crontab -l
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (/tmp/crontab.3604 installed on Tue Feb 24 12:15:13 2004)
> # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp
> $)
> 0 0-23/4 * * * /usr/bin/updatedb
> * * * * * pwd > /tmp/crontest 
> 
> 
> Also, I was able to get cron running properly on my home system (Windows
> XP Pro).  In that setup, I once again noticed that cron and its parent
> cygrunsrv processes are identified as running under SYSTEM vice unknown
> user 400 as on my office system that doesn't work.
> 
> Regards,
> 
> Wayne
> 
> -----Original Message-----
> From: Harig, Mark [mailto:maharig@idirect.net] 
> Sent: Wednesday, February 25, 2004 7:56 AM
> To: Winch Jr., Wayne S; cygwin@cygwin.com
> Subject: RE: Cron Running As UID 400
> 
> Please read the message in the Cygwin mailing list at:
> 
> http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html
> 
> It will provide you with a script that will attempt to diagnose the
> problem that you are having with cron.
> 
> 
> > -----Original Message-----
> > From: Winch Jr., Wayne S [mailto:Wayne.WinchJr@ca.com]
> > Sent: Tuesday, February 24, 2004 4:06 PM
> > To: cygwin@cygwin.com
> > Subject: Cron Running As UID 400
> > 
> > 
> > Hi,
> > 
> > I've been through a couple of problems already with cron and have 
> > resolved all of them (thanks to this list!) except this last one.  The
> 
> > cron service is indeed running, but no jobs are ever run as described 
> > in the crontab.  A strange thing I've noted is that the user that the 
> > cron service is running under is not the expected SYSTEM but the 
> > unknown 400
> > as:
> > 
> > $ ps -ef
> >      UID     PID    PPID TTY     STIME COMMAND
> >  winwa02     904       1   ?    Feb 23 /usr/X11R6/bin/XWin
> >   SYSTEM    3912       1   ?    Feb 23 /usr/bin/cygrunsrv
> >   SYSTEM    1512    3912   ?    Feb 23 /usr/sbin/inetd
> >   SYSTEM    2616       1   ?    Feb 23 /usr/bin/cygrunsrv
> >   SYSTEM    2648    2616   ?    Feb 23 /usr/sbin/cygserver
> >  winwa02    1412       1   4    Feb 23 /usr/bin/rxvt
> >  winwa02    3552    1412   5    Feb 23 /usr/bin/bash
> >  winwa02    3084    3552   5    Feb 23 /usr/bin/telnet
> >  winwa02    3228       1   2  14:16:18 /usr/bin/rxvt
> >  winwa02    3640    3228   3  14:16:19 /usr/bin/bash
> >  winwa02    3176    3640   3  15:46:35 /usr/bin/telnet
> >  winwa02    3016       1   6  16:06:23 /usr/bin/rxvt
> >  winwa02    2504    3016   7  16:06:23 /usr/bin/bash
> >  winwa02    3856       1   0  11:13:47 /usr/bin/rxvt
> >  winwa02    3576    3856   1  11:13:48 /usr/bin/bash
> >      400    2228       1   ?  12:30:59 /usr/bin/cygrunsrv
> >      400     536    2228   ?  12:30:59 /usr/sbin/cron
> >  winwa02    2188    2504   7  12:37:47 /usr/bin/ps
> > 
> > 
> > 
> > Note that other cygrunsrv processes do indeed correctly run under 
> > SYSTEM.  I suspect that if my cron and its associated parent cygrunsrv
> 
> > process were running as SYSTEM, then the cron jobs would execute per 
> > the crontab.  In fact, I manually ran /usr/sbin/cron as my user 
> > (winwa02) and cron was indeed able to kick off the crontab jobs 
> > properly.
> > 
> > A relevant entry in the Windows XP Application Event log appears in 
> > full when /usr/sbin/cron starts as:
> > 
> > The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot
> 
> > be found. The local computer may not have the necessary registry 
> > information or message DLL files to display messages from a remote 
> > computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> 
> > description; see Help and Support for details. The following 
> > information is part of the event: /usr/sbin/cron : PID 536 : (winwa02)
> 
> > ORPHAN (no passwd entry).
> > 
> > The typical command line used to install the cron service was:
> > 
> > cygrunsrv -I cron -p /usr/sbin/cron -a -D -e "CYGWIN=tty ntsec" -d 
> > "CYGWIN cron"
> > 
> > My domain /etc/passwd and /etc/group files are up-to-date.
> > 
> > As usual the output of the relevant sections of cygcheck -svr appears
> > below:
> > 
> > 
> > Cygwin Win95/NT Configuration Diagnostics Current System Time: Tue Feb
> 
> > 24 11:08:08 2004
> > 
> > Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
> > 
> > ----------snip----------
> > 
> > Output from C:\cygwin\bin\id.exe (nontsec)
> > UID: 5120(winwa02) GID: 10513(Domain Users) 10513(Domain Users)
> > 
> > Output from C:\cygwin\bin\id.exe (ntsec)
> > UID: 5120(winwa02) GID: 10513(Domain Users)
> > 544(Administrators)           
> > 545(Users)                    143344(442-SC-CRO-R)
> > 106908(98-Site)               
> > 10513(Domain Users)           162415(NASiteGroups)
> > 169978(North American Sites)
> > 
> > SysDir: C:\WINDOWS\System32
> > WinDir: C:\WINDOWS
> > 
> > CYGWIN = `tty notitle glob ntsec codepage:oem server'
> > HOME = `C:\cygwin\home\winwa02'
> > MAKE_MODE = `unix'
> > PWD = `/home/winwa02'
> > USER = `winwa02'
> > 
> > ----------snip----------
> > 
> > 
> >  1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
> >                   "cygwin1.dll" v0.0 ts=2004/1/30 16:32
> >     Cygwin DLL version info:
> >         DLL version: 1.5.7
> >         DLL epoch: 19
> >         DLL bad signal mask: 19005
> >         DLL old termios: 5
> >         DLL malloc env: 28
> >         API major: 0
> >         API minor: 109
> >         Shared data: 3
> >         DLL identifier: cygwin1
> >         Mount registry: 2
> >         Cygnus registry name: Cygnus Solutions
> >         Cygwin registry name: Cygwin
> >         Program options name: Program Options
> >         Cygwin mount registry name: mounts v2
> >         Cygdrive flags: cygdrive flags
> >         Cygdrive prefix: cygdrive prefix
> >         Cygdrive default prefix: 
> >         Build date: Fri Jan 30 19:32:04 EST 2004
> >         CVS tag: cr-0x9e
> >         Shared id: cygwin1S3
> > 
> > ----------snip----------
> > 
> > Cygwin Package Information
> > Last downloaded files to: C:\Documents and Settings\winwa02\My 
> > Documents\My Downloads\cygwin Last downloaded files from:
> ftp://mirrors.rcn.net/pub/sourceware/cygwin
> 
> Package                 Version            
> ---------- snip ----------
> cron                    3.0.1-11           
> crypt                   1.1-1              
> ctags                   5.5-4              
> cygipc                  2.03-2             
> cygrunsrv               0.98-1             
> ---------- snip ----------
> 
> Use -h to see help about each section
> 
> 
> 
> Thanks,
> 
> Wayne Sheridan Winch, Jr.
> 
> 
> --
> 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/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: Cron Running As UID 400
@ 2004-02-26 10:49 Winch Jr., Wayne S
  0 siblings, 0 replies; 7+ messages in thread
From: Winch Jr., Wayne S @ 2004-02-26 10:49 UTC (permalink / raw)
  To: Pierre A. Humblet, cygwin

 Pierre,

Somehow the permissions on my /etc/passwd and /etc/group files only gave
read permission to my account not SYSTEM.  Perhaps cron_diagnose.sh can
be updated to incorporate this checkpoint, i.e., that passwd and group
in /etc are readable by everyone.

Thanks for your help, Pierre.  Now cron jobs kick off properly and I
have telnet, ftp, etc. back again!  :-D

Cygwin rocks!

Wayne

-----Original Message-----
From: Pierre A. Humblet [mailto:Pierre.Humblet@ieee.org] 
Sent: Wednesday, February 25, 2004 3:42 PM
To: Winch Jr., Wayne S; cygwin@cygwin.com
Subject: Re: Cron Running As UID 400

At 06:18 PM 2/25/2004 -0500, Winch Jr., Wayne S wrote:
>
>Pierre,
>
>Windows Task Manager reports the user as SYSTEM for all cygrunsrv 
>processes and their children (cron, inetd, etc.).  Interestingly 
>enough, I regenerated the /etc/passwd entry for my user login on my 
>Windows XP Pro box at work and the UID field changed from what it was 
>before (after I sent the initial problem email to the Cygwin list).  
>Then, I rebooted and all Cygwin related services (cygrunsrvs) were now 
>identified as unknown user 400 in ps -ef.  As one would then expect, 
>now I do not have any capabilities associated with these services, 
>including ftp, telnet, and IPC.

At least now it's consistent! 
Is /etc/passwd readable by everybody?
Is the system mount for / (or /etc) the same as your user mount?
Is /etc/passwd on a local disk?
One way or another, SYSTEM cannot read /etc/passwd, although (going back
to your original mail), it was initially able to read it. 

>
>My /etc/passwd file has the SYSTEM, Administrators and my personal 
>account listed as:
>
>SYSTEM:*:18:544:,S-1-5-18::
>Administrators:*:544:544:,S-1-5-32-544::
>winwa02:unused_by_nt/2000/xp:70656:10513:Winch Jr., Wayne 
>S,U-TANT-A01\winwa02,S-1-5-21-2129867641-919698055-327642922-60656:/hom
>e
>/winwa02:/bin/bash

That looks OK.

>My company's domain is TANT-A01 and my username is winwa02.
>
>Also, if I type passwd, then I get the following response:
>
>$ passwd
>passwd: unknown user winwa02
>
>
>As you can see, my login entry is in /etc/passwd, but I seem to be 
>logged in as a different user, even though id reports:

Does passwd support domain users?

>$ id
>uid=70656(winwa02) gid=10513(Domain Users) 
>groups=544(Administrators),545(Users),143344(442-SC-CRO-R),106908(98-Si
>t e),10513(Domain Users),162415(NASiteGroups),169978(North American 
>Sites)
>

That's OK, you are logged in as U-TANT-A01\winwa02

Pierre

>
>>Wayne,
>>
>>The only reason why a Cygwin process runs with uid 400 is that its SID

>>was not found in /etc/passwd when first starting from Windows (you can

>>observe that by temporarily renaming /etc/passwd and starting a fresh 
>>Cygwin process).
>>It's stange that this happens only for one cygrunsrv process
>>
>>Please use the Windows Task Manager ("Processes" tab) and report the 
>>User of the strange cygrunsrv, according to Windows.
>> 
>>Pierre
>


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Cron Running As UID 400
  2004-02-26  8:51 Winch Jr., Wayne S
@ 2004-02-26 10:20 ` Pierre A. Humblet
  0 siblings, 0 replies; 7+ messages in thread
From: Pierre A. Humblet @ 2004-02-26 10:20 UTC (permalink / raw)
  To: Winch Jr., Wayne S, cygwin

At 06:18 PM 2/25/2004 -0500, Winch Jr., Wayne S wrote:
>
>Pierre,
>
>Windows Task Manager reports the user as SYSTEM for all cygrunsrv
>processes and their children (cron, inetd, etc.).  Interestingly enough,
>I regenerated the /etc/passwd entry for my user login on my Windows XP
>Pro box at work and the UID field changed from what it was before (after
>I sent the initial problem email to the Cygwin list).  Then, I rebooted
>and all Cygwin related services (cygrunsrvs) were now identified as
>unknown user 400 in ps -ef.  As one would then expect, now I do not have
>any capabilities associated with these services, including ftp, telnet,
>and IPC.

At least now it's consistent! 
Is /etc/passwd readable by everybody?
Is the system mount for / (or /etc) the same as your user mount?
Is /etc/passwd on a local disk?
One way or another, SYSTEM cannot read /etc/passwd, 
although (going back to your original mail), it was initially
able to read it. 

>
>My /etc/passwd file has the SYSTEM, Administrators and my personal
>account listed as:
>
>SYSTEM:*:18:544:,S-1-5-18::
>Administrators:*:544:544:,S-1-5-32-544::
>winwa02:unused_by_nt/2000/xp:70656:10513:Winch Jr., Wayne
>S,U-TANT-A01\winwa02,S-1-5-21-2129867641-919698055-327642922-60656:/home
>/winwa02:/bin/bash

That looks OK.

>My company's domain is TANT-A01 and my username is winwa02.
>
>Also, if I type passwd, then I get the following response:
>
>$ passwd
>passwd: unknown user winwa02
>
>
>As you can see, my login entry is in /etc/passwd, but I seem to be
>logged in as a different user, even though id reports:

Does passwd support domain users?

>$ id
>uid=70656(winwa02) gid=10513(Domain Users)
>groups=544(Administrators),545(Users),143344(442-SC-CRO-R),106908(98-Sit
>e),10513(Domain Users),162415(NASiteGroups),169978(North American Sites)
>

That's OK, you are logged in as U-TANT-A01\winwa02

Pierre

>
>>Wayne,
>>
>>The only reason why a Cygwin process runs with uid 400
>>is that its SID was not found in /etc/passwd when first
>>starting from Windows (you can observe that by temporarily
>>renaming /etc/passwd and starting a fresh Cygwin process).
>>It's stange that this happens only for one cygrunsrv process
>>
>>Please use the Windows Task Manager ("Processes" tab) and
>>report the User of the strange cygrunsrv, according to Windows.
>> 
>>Pierre
>

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Cron Running As UID 400
@ 2004-02-26  8:51 Winch Jr., Wayne S
  2004-02-26 10:20 ` Pierre A. Humblet
  0 siblings, 1 reply; 7+ messages in thread
From: Winch Jr., Wayne S @ 2004-02-26  8:51 UTC (permalink / raw)
  To: cygwin; +Cc: pierre.humblet


Pierre,

Windows Task Manager reports the user as SYSTEM for all cygrunsrv
processes and their children (cron, inetd, etc.).  Interestingly enough,
I regenerated the /etc/passwd entry for my user login on my Windows XP
Pro box at work and the UID field changed from what it was before (after
I sent the initial problem email to the Cygwin list).  Then, I rebooted
and all Cygwin related services (cygrunsrvs) were now identified as
unknown user 400 in ps -ef.  As one would then expect, now I do not have
any capabilities associated with these services, including ftp, telnet,
and IPC.

My /etc/passwd file has the SYSTEM, Administrators and my personal
account listed as:

SYSTEM:*:18:544:,S-1-5-18::
Administrators:*:544:544:,S-1-5-32-544::
winwa02:unused_by_nt/2000/xp:70656:10513:Winch Jr., Wayne
S,U-TANT-A01\winwa02,S-1-5-21-2129867641-919698055-327642922-60656:/home
/winwa02:/bin/bash

My company's domain is TANT-A01 and my username is winwa02.

Also, if I type passwd, then I get the following response:

$ passwd
passwd: unknown user winwa02


As you can see, my login entry is in /etc/passwd, but I seem to be
logged in as a different user, even though id reports:

$ id
uid=70656(winwa02) gid=10513(Domain Users)
groups=544(Administrators),545(Users),143344(442-SC-CRO-R),106908(98-Sit
e),10513(Domain Users),162415(NASiteGroups),169978(North American Sites)


Regards,

Wayne


>Wayne,
>
>The only reason why a Cygwin process runs with uid 400
>is that its SID was not found in /etc/passwd when first
>starting from Windows (you can observe that by temporarily
>renaming /etc/passwd and starting a fresh Cygwin process).
>It's stange that this happens only for one cygrunsrv process
>
>Please use the Windows Task Manager ("Processes" tab) and
>report the User of the strange cygrunsrv, according to Windows.
> 
>Pierre

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: Cron Running As UID 400
@ 2004-02-25 16:06 Harig, Mark
  0 siblings, 0 replies; 7+ messages in thread
From: Harig, Mark @ 2004-02-25 16:06 UTC (permalink / raw)
  To: Winch Jr., Wayne S, cygwin

Please read the message in the Cygwin mailing list at:

http://sources.redhat.com/ml/cygwin/2003-12/msg00711.html

It will provide you with a script that will attempt
to diagnose the problem that you are having with cron.


> -----Original Message-----
> From: Winch Jr., Wayne S [mailto:Wayne.WinchJr@ca.com]
> Sent: Tuesday, February 24, 2004 4:06 PM
> To: cygwin@cygwin.com
> Subject: Cron Running As UID 400
> 
> 
> Hi,
> 
> I've been through a couple of problems already with cron and have
> resolved all of them (thanks to this list!) except this last one.  The
> cron service is indeed running, but no jobs are ever run as 
> described in
> the crontab.  A strange thing I've noted is that the user 
> that the cron
> service is running under is not the expected SYSTEM but the 
> unknown 400
> as:
> 
> $ ps -ef
>      UID     PID    PPID TTY     STIME COMMAND
>  winwa02     904       1   ?    Feb 23 /usr/X11R6/bin/XWin
>   SYSTEM    3912       1   ?    Feb 23 /usr/bin/cygrunsrv
>   SYSTEM    1512    3912   ?    Feb 23 /usr/sbin/inetd
>   SYSTEM    2616       1   ?    Feb 23 /usr/bin/cygrunsrv
>   SYSTEM    2648    2616   ?    Feb 23 /usr/sbin/cygserver
>  winwa02    1412       1   4    Feb 23 /usr/bin/rxvt
>  winwa02    3552    1412   5    Feb 23 /usr/bin/bash
>  winwa02    3084    3552   5    Feb 23 /usr/bin/telnet
>  winwa02    3228       1   2  14:16:18 /usr/bin/rxvt
>  winwa02    3640    3228   3  14:16:19 /usr/bin/bash
>  winwa02    3176    3640   3  15:46:35 /usr/bin/telnet
>  winwa02    3016       1   6  16:06:23 /usr/bin/rxvt
>  winwa02    2504    3016   7  16:06:23 /usr/bin/bash
>  winwa02    3856       1   0  11:13:47 /usr/bin/rxvt
>  winwa02    3576    3856   1  11:13:48 /usr/bin/bash
>      400    2228       1   ?  12:30:59 /usr/bin/cygrunsrv
>      400     536    2228   ?  12:30:59 /usr/sbin/cron
>  winwa02    2188    2504   7  12:37:47 /usr/bin/ps
> 
> 
> 
> Note that other cygrunsrv processes do indeed correctly run under
> SYSTEM.  I suspect that if my cron and its associated parent cygrunsrv
> process were running as SYSTEM, then the cron jobs would 
> execute per the
> crontab.  In fact, I manually ran /usr/sbin/cron as my user (winwa02)
> and cron was indeed able to kick off the crontab jobs properly.
> 
> A relevant entry in the Windows XP Application Event log 
> appears in full
> when /usr/sbin/cron starts as:
> 
> The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot
> be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following 
> information
> is part of the event: /usr/sbin/cron : PID 536 : (winwa02) ORPHAN (no
> passwd entry).
> 
> The typical command line used to install the cron service was:
> 
> cygrunsrv -I cron -p /usr/sbin/cron -a -D -e "CYGWIN=tty ntsec" -d
> "CYGWIN cron"
> 
> My domain /etc/passwd and /etc/group files are up-to-date.
> 
> As usual the output of the relevant sections of cygcheck -svr appears
> below:
> 
> 
> Cygwin Win95/NT Configuration Diagnostics
> Current System Time: Tue Feb 24 11:08:08 2004
> 
> Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
> 
> ----------snip----------
> 
> Output from C:\cygwin\bin\id.exe (nontsec)
> UID: 5120(winwa02) GID: 10513(Domain Users)
> 10513(Domain Users)
> 
> Output from C:\cygwin\bin\id.exe (ntsec)
> UID: 5120(winwa02) GID: 10513(Domain Users)
> 544(Administrators)           
> 545(Users)                    143344(442-SC-CRO-R)
> 106908(98-Site)               
> 10513(Domain Users)           162415(NASiteGroups)
> 169978(North American Sites)
> 
> SysDir: C:\WINDOWS\System32
> WinDir: C:\WINDOWS
> 
> CYGWIN = `tty notitle glob ntsec codepage:oem server'
> HOME = `C:\cygwin\home\winwa02'
> MAKE_MODE = `unix'
> PWD = `/home/winwa02'
> USER = `winwa02'
> 
> ----------snip----------
> 
> 
>  1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                   "cygwin1.dll" v0.0 ts=2004/1/30 16:32
>     Cygwin DLL version info:
>         DLL version: 1.5.7
>         DLL epoch: 19
>         DLL bad signal mask: 19005
>         DLL old termios: 5
>         DLL malloc env: 28
>         API major: 0
>         API minor: 109
>         Shared data: 3
>         DLL identifier: cygwin1
>         Mount registry: 2
>         Cygnus registry name: Cygnus Solutions
>         Cygwin registry name: Cygwin
>         Program options name: Program Options
>         Cygwin mount registry name: mounts v2
>         Cygdrive flags: cygdrive flags
>         Cygdrive prefix: cygdrive prefix
>         Cygdrive default prefix: 
>         Build date: Fri Jan 30 19:32:04 EST 2004
>         CVS tag: cr-0x9e
>         Shared id: cygwin1S3
> 
> ----------snip----------
> 
> Cygwin Package Information
> Last downloaded files to: C:\Documents and Settings\winwa02\My
> Documents\My Downloads\cygwin
> Last downloaded files from: 
ftp://mirrors.rcn.net/pub/sourceware/cygwin

Package                 Version            
---------- snip ----------
cron                    3.0.1-11           
crypt                   1.1-1              
ctags                   5.5-4              
cygipc                  2.03-2             
cygrunsrv               0.98-1             
---------- snip ----------

Use -h to see help about each section



Thanks,

Wayne Sheridan Winch, Jr.


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Cron Running As UID 400
@ 2004-02-24 21:49 Winch Jr., Wayne S
  0 siblings, 0 replies; 7+ messages in thread
From: Winch Jr., Wayne S @ 2004-02-24 21:49 UTC (permalink / raw)
  To: cygwin

Hi,

I've been through a couple of problems already with cron and have
resolved all of them (thanks to this list!) except this last one.  The
cron service is indeed running, but no jobs are ever run as described in
the crontab.  A strange thing I've noted is that the user that the cron
service is running under is not the expected SYSTEM but the unknown 400
as:

$ ps -ef
     UID     PID    PPID TTY     STIME COMMAND
 winwa02     904       1   ?    Feb 23 /usr/X11R6/bin/XWin
  SYSTEM    3912       1   ?    Feb 23 /usr/bin/cygrunsrv
  SYSTEM    1512    3912   ?    Feb 23 /usr/sbin/inetd
  SYSTEM    2616       1   ?    Feb 23 /usr/bin/cygrunsrv
  SYSTEM    2648    2616   ?    Feb 23 /usr/sbin/cygserver
 winwa02    1412       1   4    Feb 23 /usr/bin/rxvt
 winwa02    3552    1412   5    Feb 23 /usr/bin/bash
 winwa02    3084    3552   5    Feb 23 /usr/bin/telnet
 winwa02    3228       1   2  14:16:18 /usr/bin/rxvt
 winwa02    3640    3228   3  14:16:19 /usr/bin/bash
 winwa02    3176    3640   3  15:46:35 /usr/bin/telnet
 winwa02    3016       1   6  16:06:23 /usr/bin/rxvt
 winwa02    2504    3016   7  16:06:23 /usr/bin/bash
 winwa02    3856       1   0  11:13:47 /usr/bin/rxvt
 winwa02    3576    3856   1  11:13:48 /usr/bin/bash
     400    2228       1   ?  12:30:59 /usr/bin/cygrunsrv
     400     536    2228   ?  12:30:59 /usr/sbin/cron
 winwa02    2188    2504   7  12:37:47 /usr/bin/ps



Note that other cygrunsrv processes do indeed correctly run under
SYSTEM.  I suspect that if my cron and its associated parent cygrunsrv
process were running as SYSTEM, then the cron jobs would execute per the
crontab.  In fact, I manually ran /usr/sbin/cron as my user (winwa02)
and cron was indeed able to kick off the crontab jobs properly.

A relevant entry in the Windows XP Application Event log appears in full
when /usr/sbin/cron starts as:

The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information
is part of the event: /usr/sbin/cron : PID 536 : (winwa02) ORPHAN (no
passwd entry).

The typical command line used to install the cron service was:

cygrunsrv -I cron -p /usr/sbin/cron -a -D -e "CYGWIN=tty ntsec" -d
"CYGWIN cron"

My domain /etc/passwd and /etc/group files are up-to-date.

As usual the output of the relevant sections of cygcheck -svr appears
below:


Cygwin Win95/NT Configuration Diagnostics
Current System Time: Tue Feb 24 11:08:08 2004

Windows XP Professional Ver 5.1 Build 2600 Service Pack 1

----------snip----------

Output from C:\cygwin\bin\id.exe (nontsec)
UID: 5120(winwa02) GID: 10513(Domain Users)
10513(Domain Users)

Output from C:\cygwin\bin\id.exe (ntsec)
UID: 5120(winwa02) GID: 10513(Domain Users)
544(Administrators)           
545(Users)                    143344(442-SC-CRO-R)
106908(98-Site)               
10513(Domain Users)           162415(NASiteGroups)
169978(North American Sites)

SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS

CYGWIN = `tty notitle glob ntsec codepage:oem server'
HOME = `C:\cygwin\home\winwa02'
MAKE_MODE = `unix'
PWD = `/home/winwa02'
USER = `winwa02'

----------snip----------


 1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2004/1/30 16:32
    Cygwin DLL version info:
        DLL version: 1.5.7
        DLL epoch: 19
        DLL bad signal mask: 19005
        DLL old termios: 5
        DLL malloc env: 28
        API major: 0
        API minor: 109
        Shared data: 3
        DLL identifier: cygwin1
        Mount registry: 2
        Cygnus registry name: Cygnus Solutions
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Cygwin mount registry name: mounts v2
        Cygdrive flags: cygdrive flags
        Cygdrive prefix: cygdrive prefix
        Cygdrive default prefix: 
        Build date: Fri Jan 30 19:32:04 EST 2004
        CVS tag: cr-0x9e
        Shared id: cygwin1S3

----------snip----------

Cygwin Package Information
Last downloaded files to: C:\Documents and Settings\winwa02\My
Documents\My Downloads\cygwin
Last downloaded files from: ftp://mirrors.rcn.net/pub/sourceware/cygwin

Package                 Version            
---------- snip ----------
cron                    3.0.1-11           
crypt                   1.1-1              
ctags                   5.5-4              
cygipc                  2.03-2             
cygrunsrv               0.98-1             
---------- snip ----------

Use -h to see help about each section



Thanks,

Wayne Sheridan Winch, Jr.


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-02-26  1:22 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-25 18:13 Cron Running As UID 400 Winch Jr., Wayne S
2004-02-25 18:29 ` Pierre A. Humblet
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26 10:49 Winch Jr., Wayne S
2004-02-26  8:51 Winch Jr., Wayne S
2004-02-26 10:20 ` Pierre A. Humblet
2004-02-25 16:06 Harig, Mark
2004-02-24 21:49 Winch Jr., Wayne S

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).