Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Fri, 23 May 2003 13:13:46 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Chuck Hamilton <chuckh AT softhome DOT net>
cc: cygwin AT cygwin DOT com
Subject: Re: crontab error
In-Reply-To: <000d01c3214d$79f825d0$644e8ca7@qvc.com>
Message-ID: <Pine.GSO.4.44.0305231310580.26092-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Chuck,

For the future:

On Fri, 23 May 2003, I wrote:

> Are your /etc/passwd and /etc/group files up to date?  The output of
> "cygcheck -svr" (*attached*, as per <http://cygwin.com/problems.html>)
                   ^^^^^^^^^^
> should show whether this is the case.

FYI, the output of cygcheck included as plain text produces a lot of false
positives for people searching the archives.  That's why we ask people to
*attach* the cygcheck output.
	Igor

On Fri, 23 May 2003, Chuck Hamilton wrote:

> Here is the output from cyhcheck -svr:
>
> $ cygcheck -svr
> [output of cygcheck snipped]
>
> ----- Original Message -----
> From: "Igor Pechtchanski" <pechtcha AT cs DOT nyu DOT edu>
> To: "Chuck Hamilton" <chuckh AT softhome DOT net>
> Cc: <cygwin AT cygwin DOT com>
> Sent: Friday, May 23, 2003 9:00 AM
> Subject: Re: crontab error
>
> > Chuck,
> >
> > Are your /etc/passwd and /etc/group files up to date?  The output of
> > "cygcheck -svr" (*attached*, as per <http://cygwin.com/problems.html>)
> > should show whether this is the case.
> > Igor
> >
> > On Fri, 23 May 2003, Chuck Hamilton wrote:
> >
> > > Didn't even know I was addressing a mailing list. I posted originally to
> a
> > > newsgroup. Anyway, here's the output.
> > >
> > > $ crontab -l
> > > no crontab for isscha
> > >
> > > As I said in a previous post I haven't been able to create a crontab.
> When I
> > > try I get a permissions error. See below.
> > >
> > > $ cat /tmp/crontab.1448
> > > 50 8 * * * ~isscha/bin/test.sh
> > >
> > > $ crontab /tmp/crontab.1448
> > > chown: Invalid argument
> > > $
> > >
> > >
> > > ----- Original Message -----
> > > From: Harig, Mark A.
> > > To: Chuck Hamilton
> > > Cc: cygwin AT cygwin DOT com
> > > Sent: Wednesday, May 21, 2003 3:43 PM
> > > Subject: RE: crontab error
> > >
> > >
> > > Please address all replies to cygwin AT cygwin DOT com.
> > >
> > > Please send to the mailing list the following as attachments:
> > >
> > > 1. The output of 'crontab -l' ("ell", not "one")
> > >
> > > 2. The output of 'cygcheck -srv > cygcheck.txt'
> > >
> > > This information will help readers of the mailing list to
> > > diagnose the problem that you are having.
> > > -----Original Message-----
> > > From: Chuck Hamilton [mailto:chuckh AT softhome DOT net]
> > > Sent: Wednesday, May 21, 2003 3:13 PM
> > > To: Harig, Mark
> > > Subject: Re: crontab error
> > >
> > >
> > > Here's what I get...
> > >
> > > Your computer does not appear to have a crontab for isscha.
> > > Please generate a crontab for isscha using 'crontab -e',
> > > and run this script again.
> > >
> > > So I again try to generate a crontab with just a comment line in it and
> get
> > > this...
> > >
> > > $ crontab -e
> > > crontab: installing new crontab
> > > chown: Invalid argument
> > > crontab: edits left in /tmp/crontab.1660
> > >
> > >
> > > ----- Original Message -----
> > > From: "Harig, Mark A." <maharig AT idirect DOT net>
> > > To: "Chuck" <chuckh AT softhome DOT net>; <cygwin AT cygwin DOT com>
> > > Sent: Wednesday, May 21, 2003 12:06 PM
> > > Subject: RE: crontab error
> > >
> > >
> > > Please run the attached script.
> > > It will check some file permissions
> > > and other details that need to be
> > > set up properly in order for cron to
> > > work.  It does NOT change anything
> > > on your computer, but only diagnoses.
> > > You may need to run it several times
> > > until it completes successfully (it
> > > will stop any time it finds a problem
> > > and report to you what problem needs
> > > to be corrected).
> > >
> > > > -----Original Message-----
> > > > From: Chuck [mailto:chuckh AT softhome DOT net]
> > > > Sent: Wednesday, May 21, 2003 9:27 AM
> > > > To: cygwin AT cygwin DOT com
> > > > Subject: crontab error
> > > >
> > > >
> > > > I need a little help getting cron to work. My apologies if
> > > > this is answered
> > > > somewhere else but I haven't been able to find it.
> > > >
> > > > I've installed cron as a win2k service using "cygrunsrv -I cron -p
> > > > /usr/sbin/cron -a -D -d "Cygwin cron" -e "CYGWIN=tty ntsec" "
> > > > as suggested
> > > > in another post. When I try to start the service I get "Could
> > > > not start the
> > > > cygwin cron service on local computer. The service did not
> > > > return an error.
> > > > This could be an internal Windows error or an internal service error."
> > > >
> > > > When I try to create a crontab file with "crontab -e" and
> > > > save it I get the
> > > > following error "chown: Invalid argument".
> > > >
> > > > What do I need to do to fix these?

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) 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/