From: "Harig, Mark A." <maharig@idirect.net>
To: "Eric De La Cruz Lugo" <eric_delacruz@yahoo.com>, <cygwin@cygwin.com>
Subject: RE: cron problem in W2K Proffesional
Date: Fri, 06 Dec 2002 13:30:00 -0000 [thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E7630D7@ex02.idirect.net> (raw)
Also, once you have done this, shut down
your cron service and restart it.
> -----Original Message-----
> From: Harig, Mark A.
> Sent: Friday, December 06, 2002 4:20 PM
> To: Eric De La Cruz Lugo; cygwin@cygwin.com
> Subject: RE: cron problem in W2K Proffesional
>
>
> >
> > drwxrwxrwx 3 asuncion Ninguno 0 Apr
> > 12 2002 /var/cron
> >
> > drwxrwxrwx 2 asuncion Ninguno 0 Dec 6
> > 13:04 /var/cron/tabs
> >
>
> For some reason, your 'sticky bit' settings didn't get set
> for /var/cron/ and /var/cron/tabs/.
>
> Instead of 'drwxrwxrwx', your permissions should be
> 'drwxrwxrwt'.
>
> Try:
>
> chmod 1777 /var/cron
> chmod 1777 /var/cron/tabs
>
> ----
>
> --
> 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/
>
>
--
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/
next reply other threads:[~2002-12-06 21:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 13:30 Harig, Mark A. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 16:07 Harig, Mark A.
2002-12-06 20:53 ` Eric De La Cruz Lugo
2002-12-09 17:10 ` Andrew DeFaria
2002-12-06 15:14 Harig, Mark A.
2002-12-06 15:52 ` Eric De La Cruz Lugo
2002-12-06 13:24 Harig, Mark A.
2002-12-06 12:04 Harig, Mark A.
2002-12-06 12:05 ` Eric De La Cruz Lugo
2002-12-06 14:03 ` Eric De La Cruz Lugo
2002-12-06 11:21 Eric De La Cruz Lugo
2002-12-06 11:02 Harig, Mark A.
2002-12-06 8:51 Eric De La Cruz Lugo
2002-12-06 9:07 ` Christopher Faylor
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=BADF3C947A1BD54FBA75C70C241B0B9E7630D7@ex02.idirect.net \
--to=maharig@idirect.net \
--cc=cygwin@cygwin.com \
--cc=eric_delacruz@yahoo.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).