public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ryan T. Sammartino" <ryants@shaw.ca>
To: cygwin@cygwin.com
Subject: Re: cron doesn't run (was: Re: login and ssh: can't authenticate)
Date: Tue, 11 Dec 2001 11:36:00 -0000	[thread overview]
Message-ID: <20011211191025.GA14863@localhost> (raw)
In-Reply-To: <20011211170730.Y740@cygbert.vinschen.de>

On Tue, Dec 11, 2001 at 05:07:30PM +0100, Corinna Vinschen wrote:
> 
> 	Everyone:*:0:0:,S-1-1-0::
> 	Administrators:*:544:544:,S-1-5-32-544::
> 
> to
> 
> 	Everyone:*:1:1:,S-1-1-0::
> 	root:*:0:0:,S-1-5-32-544::
> 
<snip>


Tried all that, didn't help me.


> The shell and the home directory are set up correctly for my
> users in /etc/passwd.  Paths are given in POSIX notation.  I
> never use /cygdrive paths in /etc/passwd.  I'm always setting
> CYGWIN to `binmode tty ntsec' in the system environment.  All
> important mount points are binary system mounts.  I don't expect
> shares to work for processes changing the user context w/o
> password and I don't expect to have user mount points then.

Check.  All of that is true for me as well, except I don't have
"binmode" in my CYGWIN.


> 
> I'm always looking for the permissions of the concerned files and
> directories.  SYSTEM must have permission to read all files in
> /var/cron for example.  SYSTEM must have read permisssion on /etc
> and the important files in it.  

Check.  Like I said, sshd works perfectly for me now, so I'm pretty
sure all the 'ntsec' and SYSTEM stuff is OK.  I'm pretty sure
SYSTEM can read everything under /var/cron, because I see "RELOAD
tabs/ryans" in the event logs.


> Hope that helps.  I'm really getting tired of answering that sort
> of mail.  Everything should be in the mailing list archive now.

I know the feeling :)  Unfortunately, some crucial step is missing, or
something has changed recently that is causing it to break.


-- 
Ryan T. Sammartino (ryants@shaw.ca)
http://members.shaw.ca/ryants/
paranoia, n.:
	A healthy understanding of the way the universe works.

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

  reply	other threads:[~2001-12-11 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11  7:07 ASH, JAMES (SBCSI)
2001-12-11  8:38 ` Corinna Vinschen
2001-12-11 11:36   ` Ryan T. Sammartino [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11  7:06 ASH, JAMES (SBCSI)
2001-12-07 16:50 login and ssh: can't authenticate Ryan T. Sammartino
2001-12-08  3:14 ` Corinna Vinschen
2001-12-10 13:52   ` cron doesn't run (was: Re: login and ssh: can't authenticate) Ryan T. Sammartino
2001-12-10 15:30     ` Ryan T. Sammartino
2001-12-11  0:27       ` Corinna Vinschen
2001-12-11  9:47         ` Ryan T. Sammartino
2001-12-12 11:51         ` Ryan T. Sammartino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011211191025.GA14863@localhost \
    --to=ryants@shaw.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).