public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Subject: Re: CRON problems
Date: Fri, 07 May 2004 15:06:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0405071043460.5892@slinky.cs.nyu.edu> (raw)
In-Reply-To: <409B3999.94026545@dessent.net>

On Fri, 7 May 2004, Brian Dessent wrote:

> Andrew DeFaria wrote:
>
> >   # Install cron service:
> >   cygrunsrv -I cron -p /usr/sbin/cron -a -D -d "Cygwin cron" -e "MAILTO=$USER@Salira.com" -e "CYGWIN=ntsec"
>                                                                                                ^^^^^^^^^^^^^^
> As an aside, hasn't 'ntsec' been enabled by default for a long time
> now?  Or am I just remembering incorrectly?
>
> Brian

You are remembering correctly -- "ntsec" was enabled by default back in
the 1.3.* days.  That makes the above redundant but harmless.  Having
"ntsec" in your $CYGWIN also serves as reminder/documentation for the
actual option values (even if they are the default).
	Igor
-- 
				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/

  reply	other threads:[~2004-05-07 14:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 22:47 Harig, Mark
2004-05-06 23:42 ` Hank Statscewich
2004-05-07  0:14   ` Igor Pechtchanski
2004-05-07  0:52     ` Hank Statscewich
2004-05-07  2:06       ` Brian Dessent
2004-05-07  6:55         ` Andrew DeFaria
2004-05-07  8:21           ` Brian Dessent
2004-05-07 15:06             ` Igor Pechtchanski [this message]
2004-05-07 15:23               ` Andrew DeFaria
2004-05-07 15:53                 ` Igor Pechtchanski
2004-05-07 20:08                   ` Andrew DeFaria
2004-05-07 15:20             ` Andrew DeFaria
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 22:18 cron problems Charles Miller
2008-05-14 22:28 ` Pierre A. Humblet
2007-11-06 15:30 Helge Stenström
2007-11-06 15:56 ` Pierre A. Humblet
2007-05-14 14:45 CRON problems sabbella
2007-05-14 17:39 ` Pierre A. Humblet
2006-07-24 23:29 Cron Problems Andrew King
2006-07-24 23:38 ` René Berber
2004-05-07 15:17 CRON problems Harig, Mark
2004-05-07 15:15 Harig, Mark
2004-05-07 15:20 ` Igor Pechtchanski
2004-05-07 15:12 Harig, Mark
2004-05-06  0:16 Hank Statscewich
2003-01-23 10:47 Cron Problems Wu Yongwei
2003-01-23 11:01 ` Elfyn McBratney
2003-01-23  6:24 Wu Yongwei
2003-01-23  9:48 ` Elfyn McBratney
2001-10-31  8:51 cron problems Lou Rayman

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=Pine.GSO.4.56.0405071043460.5892@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --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).