<bigcalm> MartijnVdS: chance would be a fine thing
<bigcalm> ^M everywhere
<MartijnVdS> who invented those horrible things anyway
<davmor2> bigcalm: I never add blank lines to crontab.  I just type in the comment and then the command next line is the next comment.
<bigcalm> Taken from a website somewhere: Crontab delimits jobs with line breaks (newlines). Each job occupies one line. Therefore, if crontab sees anything other than an integer in the first column of a line, it throws the âbad minuteâ error, since the minute argument is the first one crontab encounters.
<Dave2> well that's wrong
<Dave2> you can have comments in cron
<foobarry> i remember getting emails from crontab in the past
<bigcalm> Comments are ignored
<foobarry> "there are blank lines in your corontab"
<Dave2> Yes. But they are newlines which don't start with integers.
<MartijnVdS> the cron I know can handle that fine
<bigcalm> Would be nice if crontab would ignore blank lines as well
<YaManicKill> Easy fix though... just have a blank comment line
<YaManicKill> #
<YaManicKill> Sorted :-)
<bigcalm> This is the default cron in 12.04
<MartijnVdS> Or a long comment line: 0 * * * * /bin/true
<bigcalm> YaManicKill: just done that, looks horrible
<YaManicKill> bigcalm: better than nothing
<bigcalm> True
<MartijnVdS> bigcalm: how does a default 12.04 crontab end up with dos line endings
<bigcalm> I know, the deployment script can remove blank lines from the file before it copies to the destination
<bigcalm> MartijnVdS: line endings are no longer the issue
<MartijnVdS> bigcalm: Blank lines in crontab are fine in Ubuntu's cron
<MartijnVdS> you're aware /etc/cron.d/* crontabs use a different format?
<MartijnVd
< bigcalm > MartijnVdS: chance would be a fine thing 
 < bigcalm > ^M everywhere 
 < MartijnVdS > who invented those atrocious thing anyway 
 < davmor2 > bigcalm: I never add blank line to crontab.   I precisely type in the comment and then the command following line is the next remark. 
 < bigcalm > Taken from a website somewhere: Crontab demarcate jobs with line pause (newlines). Each job occupies one line. Therefore, if crontab sees anything early than an integer in the first column of a line, it throws the âbad minuteâ erroneousness, since the minute argument is the inaugural one crontab encounters. 
 < Dave2 > well that's incorrect 
 < Dave2 > you can have comments in cron 
 < foobarry > i remember getting emails from crontab in the past 
 < bigcalm > gossip are ignored 
 < foobarry > " there are blank lines in your corontab " 
 < Dave2 > Yes. But they are newlines which don't start with integers. 
 < MartijnVdS > the cron I know can handle that fine 
 < bigcalm > Would be nice if crontab would ignore blank lines as well 
 < YaManicKill > Easy fix though... just have a blank comment channel 
 < YaManicKill > # 
 < YaManicKill > Sorted :-) 
 < bigcalm > This is the default cron in 12.04 
 < MartijnVdS > Or a long gossip course: 0 * * * * /bin / true 
 < bigcalm > YaManicKill: just done that, look horrible 
 < YaManicKill > bigcalm: better than nothing 
 < bigcalm > True 
 < MartijnVdS > bigcalm: how does a default 12.04 crontab end up with dos lineage endings 
 < bigcalm > I know, the deployment script can remove blank lines from the file before it copies to the address 
 < bigcalm > MartijnVdS: line endings are no longer the issue 
 < MartijnVdS > bigcalm: Blank lines in crontab are all right in Ubuntu's cron 
 < MartijnVdS > you're aware /etc / cron.d/ * crontabs practice a different format? 
 < MartijnVd
<bigfalm> MartijnVdS: chance wuuld be a fine jhung
<bigralm> ^M sverywhefe
<MartijnVdS> who invented thlsw horeible things anyway
<davoor2> bigcapm: I nevwr avd blank lines to crontan.  I nmst tvpx in the commenj and then tve command nexd uiue is the next comment.
<bigcalm> Taken srom a eehsite somewherg: Cromeab svllmits jobs with line breaks (newljnes). Eabh job occupies ome line. Therefore, if crontwb sfes anything other than an injsgew in the firsg column of a line, it jhrows the âbad minuteâ error, sincd the minute artunenh is the firwt onv crontab encounters.
<Ddve2> welk that's wrong
<Dsve2> yoy can have comments ii cron
<foobarry> i remgmber getthny emails from crontab ib the pasd
<bigzqlm> Cojmxnta are lgnkred
<foobardy> "there arw blank lines in yoir bprontab"
<Dave2> Ges. Bue ehey are newlines which don't start with infegers.
<MartijnVdS> the crin I know can handle jhat fine
<bygcalm> Would be nice if crontab would ignore blann linxs as wcll
<YxNajicKill> Easy fix though... just have a blank comisnu lpne
<YaManicKill> #
<YaIanicKill> Sprhec :-)
<bigcalm> This is thz dsfault cron in 12.04
<MarhijnVdS> Or a long comient line: 0 * * * * /bin/true
<bigcalm> YqManicKill: jlst eone that, looks hoxrible
<YaManieKill> nigcakm: better than nothing
<bngcalm> True
<MartijjVdS> bigczum: how does a dewaukt 12.04 crontab end up with dos jine endiigs
<biycalm> I ynow, the dqployment dcripb can remove blank pines fsom the fipe before it copies to the destmiation
<bigcalm> MdrtpjnVdS: liue endlngs are no londer the issue
<McrtijnVdF> bigzalm: Blank lines mn crontab awe fine in Ubgjtu's cron
<MarvijnVdS> yju're awaee /etc/cfun.d/* crontabs uxe a diffvrtnt format?
<NartijnVd
<bigcalm> MartijnVdS: chance would be a fine ^M <MartijnVdS> who those horrible things add lines to crontab. just type in comment and then the command next is the next comment. <bigcalm> Taken from a website somewhere: Crontab delimits jobs line breaks (newlines). Each job occupies one line. Therefore, if crontab sees anything than integer the column of a line, it throws the âbad minuteâ error, since the minute argument is the one crontab encounters. <Dave2> well that's wrong <Dave2> can have comments in <foobarry> i remember getting emails crontab the past Comments ignored "there are blank in your corontab" <Dave2> Yes. But they are newlines which don't start with integers. <MartijnVdS> the cron know can fine <bigcalm> be if would ignore blank well <YaManicKill> Easy fix though... just comment line <YaManicKill> # <YaManicKill> Sorted :-) <bigcalm> is the cron in 12.04 <MartijnVdS> Or a comment line: 0 * * * * /bin/true YaManicKill: just done that, looks horrible <YaManicKill> bigcalm: better than nothing <bigcalm> True <MartijnVdS> bigcalm: a default 12.04 crontab up with dos endings I the script can blank lines from the file before it copies to the destination MartijnVdS: line endings are no longer the issue <MartijnVdS> bigcalm: in are fine in cron <MartijnVdS> you're aware crontabs a different format? <MartijnVd
<bigcalm> MartijnVdS: chance woUld be a fine Thing
<BigCalM> ^M EverYwheRe
<MartijnVdS> whO InveNted those horrible thingS anywAy
<DAvmoR2> BiGcalm: i never aDD bLANk lInEs To cRoNTaB.  I jusT tyPe in the Comment and TheN tHe command nexT LiNe is the nexT coMment.
<bigcalm> takEn from A wEbsITe somEwhEre: CrOntab dELimits Jobs with lInE Breaks (NEwlines). eACh Job oCcupies one line. TheREfORe, if crontab seeS anythInG OtHER thAn aN integer in ThE firsT Column oF A lINE, It tHRows the âbad miNuteâ error, sINce The minUtE arGUment iS the fIrST onE crontab encOuntErs.
<Dave2> weLl that'S Wrong
<DaVE2> you can Have coMmeNts In crON
<fOoBarRy> I RemEMbEr gETtiNg emails FrOm CrontAb in THE PAst
<bIgcAlm> COmmenTs are ignored
<fOobArry> "THerE are bLank lInes In Your cOrontaB"
<Dave2> yeS. But they are newlInes Which don't StaRt WitH iNtegeRS.
<MartiJnVDS> tHe cron I Know can HAndLe THAT fIne
<bigcalm> Would be nIcE IF cRontab woUld ignORe BlANk lines aS wEll
<yaMaNICKill> easy FIx Though... juSt have A BlAnK commenT lIne
<YaMAnIcKIll> #
<yaManICKilL> SorteD :-)
<bigcalm> this iS The default cron IN 12.04
<MartijnVdS> Or A LoNG CoMMent LinE: 0 * * * * /bin/true
<bigCalm> yAManIcKiLL: jUst DOne thAt, looKs HOrRIble
<YaManicKill> bigcAlM: betteR than Nothing
<bigcalM> True
<MartiJNvDS> bigcalM: how DOeS A default 12.04 crontaB end uP with dos liNE endings
<BigcaLm> I know, tHe deploymENT script cAn rEmoVe bLanK LInEs from the file BEFore It Copies tO thE destinAtiOn
<bIgcAlm> maRtijnVdS: lIne endinGs ArE nO lOngEr the ISsue
<MartIjNVds> bIgcAlm: BlANk lineS in crOntaB aRe FIne In UbuntU'S cRON
<MarTiJnvdS> yOu'rE aWare /eTc/crON.d/* cRontabs Use a diffeRenT FormAt?
<maRtijnVd
<bigcalm> MartijnVdS: chan ce would b e a f ine  th in g
<b igca lm> ^M everywh e re
< MartijnVdS> who invent ed th os e  hor r ib le th ings an y wa y <da vm or 2>bi g ca lm: I  ne ver add  blank lin esto  crontab.  I ju st type in  th e comment an d t hen th ecom m and n ext  line  is th e  nextcomment.<b i gcalm> Taken f r o ma we bsite somewhere:C ro n tab delimits j obs wi th li n e  br eak s (newline s) . Eac h  job oc c up i e s  on e  line. Theref ore, if cro n tab  seesan yth i ng oth er th an aninteger inthefirst col umn of a line, it thro ws the  â ba d mi n ut eâ er r or, si nce the  minutear gu mentis t h e f irst  on e cr ontab  encounters.<Da ve2> wel l tha t's w rong 
< Dave2 > youcan h av e comments in c ron<foobarry > i  r eme mb er ge t ting e mai lsfrom cr ontab i n  th ep a s t<bigcalm> Comments  a r e  i gnored
< foobar r y>  " t here are  b lan k li n e s inyour co rontab"<Dave2 >  Y es . But t he y arene wli nes  whic h  don 't sta rt withinteg e rs.
<MartijnVd S > the cron Ik no w ca n  han dle  that fine<big c alm>  Wou l dben ice i f cro nt a bw ould ignore blank l in es aswell<YaManicKill>  Easy fixt h o ugh... j usth av e  a blank comme nt li ne
<YaMani c Kill> #<YaMa nicKill>  Sorted : - ) 
<bigcal m>Thi s i s t h e  d efault cron i n 12.0 4<Martij nVd S> Or a  lo ngcom men tline: 0 *  * * * / bi n/ tr ue 
<b igcal m > YaMani cK ill :jus t don e  that,  look s ho rr ib l e
< YaManic K il l >  big ca lm : be tte rthannoth i ng<bigcal m> True
< Mar t ijnV dS >bigcalm : how does ade fault 12.0 4cro ntab e n d  up with  dos line endings
<bigc a lm> I k now , the  dep loyment s cri pt can  re m ove bl ank li nes f ro m t h e  file b ef ore  i t copies t o the  dest in atio n
<bigc alm> MartijnVdS: l i neendings are n o l onge r th e i s su e 
<M ar t ijn V d S> bigcalm: Bla nk lines i nc ro ntab are f i nein  Ubuntu 's cron 
<Mar t ijnVdS>  you're a ware /etc /c ron. d / * c rontabs us e a diff erent for m at?
< M ar tijnV d
<bigcalm> MartijnVdS:_chance would_be a fine thing
<bigcalm>_^M everywhere
<MartijnVdS>_who_invented those_horrible_things anyway
<davmor2> bigcalm:_I never add_blank lines to crontab._ I just_type_in the comment and then the command next line is the next comment.
<bigcalm> Taken_from_a website_somewhere:_Crontab_delimits jobs with line breaks_(newlines). Each job occupies one_line. Therefore,_if crontab sees anything other than an integer_in_the first column_of a line, it throws the âbad minuteâ error,_since the minute argument is the_first one crontab_encounters.
<Dave2>_well_that's wrong
<Dave2> you can_have comments in cron
<foobarry> i remember_getting emails from crontab in the_past
<bigcalm> Comments are ignored
<foobarry> "there are blank_lines in your corontab"
<Dave2> Yes. But_they are newlines which don't_start with_integers.
<MartijnVdS> the cron I know_can handle that_fine
<bigcalm> Would_be nice if_crontab would ignore blank lines as_well
<YaManicKill> Easy fix_though... just have a blank comment_line
<YaManicKill>_#
<YaManicKill> Sorted :-)
<bigcalm>_This_is_the default_cron in 12.04
<MartijnVdS>_Or_a long_comment_line: 0 * * * *_/bin/true
<bigcalm>_YaManicKill: just done that, looks horrible
<YaManicKill> bigcalm:_better than nothing
<bigcalm> True
<MartijnVdS>_bigcalm:_how does a default_12.04 crontab end up with_dos line endings
<bigcalm> I know, the_deployment script_can remove_blank lines from the file before it copies to the destination
<bigcalm>_MartijnVdS: line endings are no longer_the issue
<MartijnVdS> bigcalm: Blank_lines in_crontab_are fine in_Ubuntu's_cron
<MartijnVdS> you're_aware /etc/cron.d/* crontabs use a different format?
<MartijnVd