I am very impressed by the oratary skills you have all shown in this
discussion... but please... can this thread be terminated soon?

quoted text
> > On Sat, 20 Feb 2010, Paul M wrote:
> >
> >> it's **Not clear whatproblem you're actualy trying to solve.**
> >>
> > What's so difficult about "need a way to edit crontab with something 
> > like
> > an nCurses" interface? That seems to be, by definition, simple,
> > point-and-click, definate options, no man pages, no vi editors, ...
> >
> >> I can imagine a situation where your question is valid and sensible, 
> >> but
> >> that would be just be me going off on a tangent - give us some
> >> background, explain *properly* why the answers you've been given are
> >> unsatisfactory.
> >> I have to say, it does sound to me as if you're being deliberately
> >> obtuse.
> >>
> > Certainly not intended, .. however I cannot imagine why the statment 
> > above
> > does not describe the problem accurately & succinctly.
> 
> This seems to be the crux of the problem.
> To you the question is accurate and succinct - to most others who have 
> responded.
> it is not. Who is right and who is wrong? who cares, point is we need 
> the full
> story, even if you dont understand why.
> 
> 
> paulm
> 
> 
> One more point to make, I dont know if it has any relevance, I'm just
> inventing a situation here in the absense of the full story. If it 
> doesnt
> apply, then just ignore.
> 
> If you impliment a graphical ui which gives uneducated/inexperienced 
> 'admins'
> unrestricted (remote) access to root's crontab, that would be 
> incredibly stupid.
> If you do impliment a system, (either your own or an existing tool) 
> then it
> should have proper access controls and validity checking to ensure they 
> can
> only change the info that they should be changing. This probably means 
> rolling
> your own.