This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Crontab problems

--- Raphael <> wrote:
> On Sun, Sep 15, 2002 at 06:49:48AM -0700, Nicholas Wourms wrote:
> > 
> > --- Raphael <> wrote:
> >  > Great but without any C knowledge I wouldn't even know where
> to
> > > start. I'm 
> > > wondering, if Corinne is reading this, if the patch might not
> be
> > > standarized 
> > > for Cygwin considering the interchangability between Cygwin and
> > > Windows.
> > > Ofcourse only if there is really no security issue.
> > > 
> > > > Boy, I get to quote the source a lot these days...  Not that
> I'm
> > > > complaining or anything... :-D
> >  
> > > I'm sure everyone is very greatfull for you sharing this
> > > information. It's
> > > considarably more informative than a blunt ?Use vi.exe? some
> people
> > > try
> > > to kill a thread with. Thank you very much.
> 1st. I hereby ask you kindly and publicly, to refrain from sending
> any 
> more mails to my personal address. If you want to reply to the list
> thats
> fine by me, but stop cc-ing to my personal address. That said....

Well too bad.  As Earnie Boyd once said:
"In response to this email I hit Reply-All.  If you don't set
then this email is sent to you in response and the list is CCed.  I
and others don't adjust the distribution as I/we can't remember the
names of the 1000's of people on this list.  It's you who needs to
adjust the headers not me or someone else."

Definitely sums up how I feel.
> > Paul Vixie last released cron in freakin' 1994 (or thereabouts)! 
> Not
> > much has been done to modify it since then.  I'm sure his design
> was
> > quite appropriate at the time, when the thought of using a gui
> editor
> > to edit cron jobs was unheard of.
> Makes you think doesn't it. Might anything have changed since then?

Jeeze, that's the point!  Nothing has changed because it is highly
stable.  That is not something to scoff at, it something to be
> > The point is: why make life
> > difficult for yourself?  If you want a lazy editor, use nano or
> pico
> > for crying out loud!
> > They're so easy my grandmother could use them.
> Your assumptions are based on extreme prejudice.

No, my assumptions are based on the philosophy of some of those who
put the Posix standards in place.  The whole idea is to use the right
tool for the right situation to get the job done efficiently. 
Expecting crontab to use a gui editor is overkill and will likely
introduce instability into the system.  However, using it edit source
code, makefiles, startx, etc. is perfectly fine.

> > Trying to use Windows NotePad, which introduces the whole \r\n
> deal,
> > is friggin' crazy!
> Your reading is 'friggin crazy'. In fact I'm using TextPad, a fine
> editor
> that has no problems whatsoever with \r\n as it is very able to
> recognise
> what kind of file it is editing.

But it is still a Windows app which has no bindings to Cygwin, so in
order to make it work, the i/o of crontab will need to be changed. 
Thus, it will introduce possible instabilities into a piece of
software which is extremely reliable at the moment.  It's called
"Don't fix it if it isn't broken".  AFAICT, cron is working within
specified parameters.  I'm sure 90% of the people out there would
> > Why should Corinna, or anyone else for that
> > matter, patch the *working* cron sources just for *you* when
> there
> > are perfectly good tools already available?
> I don't know, I was under the impression that the interoperabilty
> between
> Windows programs and Cygwin where of high priority. If I'm not
> mistaken
> I have seen several times statements written here that cygwin is no
> *nix
> and has no intention to become one. In fact thats logical becouse
> then one
> might better take the step to any *nix instead of bothering with a
> hybrid.
> > I'm sorry my friend,
> I'm not your friend, nor is it very likely that I will ever become
> one.

Obviously you aren't aware of sarcasm when it is directed at you...

> > but
> > this isn't Burger King, where you can have it your way right
> away.
> What gave you the impression I would like to have my way right
> away?

Well, in a follow up message, earlier in this thread, you stated
If Corinna was reading this that she should investigate and patch the
code to work for you.

Again, nobody else seems to have a problem with not wanting to use
the tools that come with the toolkit...  Only you.  Wonder why that

> > I
> > applaud Igor for being generous and doing the research for you,
> but I
> > don't think you should expect it every time.  I think you read
> too
> > much into "use vi".  It was simply providing a sensible
> alternative
> > to Windows NotePad which provides the same functionality without
> the
> > need for modifing *working* sources.  If that doesn't suit you,
> > TextPad looks like a viable alternative...
> How thick are you anyway? Haven't you understood anything of 
> Igor's splendid explanation. You who are preaching the most about
> reading
> and research on this list seem to fail the exercise completely.
> Might 
> highschool be a good advise? It might help you to prevent more of
> these
> painfull mistakes.

What does this have to do with anything?  As far as I see it, you
asked a question that implied you had done no research.  You didn't
follow the guidelines by even giving us a hint about what you had
already done to investigate the situation.  The facts in your case
were scare if non-existant.  I suggest you considier learning the
scientific method, as it would give you the ability to produce better
bug reports.

> > Cheers,
> > Nicholas
> Sure blame it on the alcohol.

Well I don't drink, so I really wouldn't know.  You might want to
keep off the crack rock though...

Do you Yahoo!?
Yahoo! News - Today's headlines

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]