From: Corinna Vinschen <corinna.vinschen@cityweb.de>
To: js@ddre.dk, cygwin@sourceware.cygnus.com
Subject: Re: cron 2.9.2
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <36C3611E.1D2487D9@cityweb.de> (raw)
Message-ID: <19990228230200.JvNO6xgO6fskXTCk9cmwWveYUqbrajIrZLOxZf91UEY@z> (raw)
In-Reply-To: <2991B60B9F72D011811C0000F821BB4C50B967@FREJA>
Hi Jens,
js@ddre.dk wrote:
> You should include the following in your documentation :
>
> Requirements:
>
> /etc/passwd
> /bin/sh
This is already mentioned in the man page `crontab.5'.
> An example passwd file would be appreciated
Call `mkpasswd' from cygwin distribution for getting a passwd file.
> and also an example crontab
> file, using a lot of NT specific syntax in the command field.
I don't know, what you mean with `NT specific syntax'. The syntax is
compatible to Vixie cron 3.0.1, which is part of Linux distributions.
In fact, two features are missing:
- The support of setting environment variables in crontab file and
- the support of the file `/etc/crontab'.
Both are planned for a future release.
> One bug allthough
>
> crontab -l
>
> doesn't generate a proper (CRLF seperated) output.
I'm using standard output mode of stdout in this case. Don't know, why this
should happen, if you haven't set CYGWIN=...binmode...
> It would also be nice if the -u flag (user) is implemented for crontab.
This is part of a NT security problem. I can't explain it in detail now,
but I'm working on a solution already.
>
> Anayway, thanks for a very nice implementation, I have been looking for
Thank you!
Corinna
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next parent reply other threads:[~1999-02-28 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2991B60B9F72D011811C0000F821BB4C50B967@FREJA>
1999-02-11 15:12 ` Corinna Vinschen [this message]
1999-02-28 23:02 ` Corinna Vinschen
[not found] <2991B60B9F72D011811C0000F821BB4C50B966@FREJA>
1999-02-08 13:20 ` Corinna Vinschen
1999-02-28 23:02 ` Corinna Vinschen
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=36C3611E.1D2487D9@cityweb.de \
--to=corinna.vinschen@cityweb.de \
--cc=cygwin@sourceware.cygnus.com \
--cc=js@ddre.dk \
/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).