Todd C. Miller <[email protected]> wrote: > > --- usr.sbin/cron/crontab.5 > > +++ usr.sbin/cron/crontab.5 > > @@ -193,14 +193,27 @@ will be changed into newline characters, and all data > > after the first > > .Ql % > > will be sent to the command as standard input. > > +.Pp > > +If the > > +.Ar command > > +field begins with > > +.Ql -n , > > +the execution output will only be mailed if the command exits with a > > non-zer > > o > > +exit code. > > +No mail is sent after a successful run. > > +The > > +.Ql -n > > +option is an attempt to cure potentially copious volumes of mail coming > > from > > +.Xr cron 8 . > > If the > > .Ar command > > field begins with > > .Ql -q , > > execution will not be logged. > > Use whitespace to separate > > -.Ql -q > > -from the command. > > +.Ql -n , > > +.Ql -q , > > +and the command. > > .Pp
I would prefer if the -q and -n descriptions were in a table. I dislike the ancient style of describing such things inline (harder to spot). And it really falls down when there are multiple ones. How do you feel about that jmc? Also, do -qn and -nq work? How about -nnn. Not saying those make a lot of sense, but once getopt syntax is borrowed it should probably be honoured.
