-20
<SpamapS> tmike: the test suite is not meant to be run as root, in fact I believe it is meant to fail as root
<SpamapS> tmike: there's one fail that is no big deal, just a different error message. The one where len is expected to be 13 and is 0 looks more serious.
<pmjdebruijn> hi
<pmjdebruijn> are there known issues with upstart and lots of file descriptors?
<pmjdebruijn> I'm running dansguardian -N (=foreground) from an upstart job
<pmjdebruijn> with 4000 file descriptors
<pmjdebruijn> seems to work fine from the init script
<pmjdebruijn> though I'm wondering if upstart ignores the ulimit I have in there... and/or the security/limits.conf
<jodh> pmjdebruijn: upstart doesn't have pam support so limits.conf is not used.
<pmjdebruijn> ah ok
<pmjdebruijn> but settings ulimit -n in the pre-start script doesn't seem to help either
<jodh> pmjdebruijn: that's because the pre-start is run as a process so any other process spawned from that job won't be affected by what you do in pre-start.
<jodh> pmjdebruijn: You need the limit stanza - http://upstart.ubuntu.com/cookbook/#limit
<jodh> pmjdebruijn: init(5) for full details.
<pmjdebruijn> jodh: that makes sense, but the squid package in maverick has ulimit set in pre-start
<jodh> pmjdebruijn: sounds like you found a bug then ;-)
<pmjdebruijn> heh
<jodh> pmjdebruijn: still seems to be a problem in precise: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/squid/precise/view/head:/debian/squid.upstart Could you raise a bug on this? (so you get the kudos :) - https://bugs.launchpad.net/ubuntu/precise/+source/squ
-20 
 < SpamapS > tmike: the test suite is not meant to be run as ancestor, in fact I think it is meant to fail as root 
 < SpamapS > tmike: there's one fail that is no boastful batch, just a different erroneousness message. The one where len is expect to be 13 and is 0 looks more dangerous. 
 < pmjdebruijn > hi 
 < pmjdebruijn > are there known topic with upstart and lots of file descriptors? 
 < pmjdebruijn > I'm running dansguardian -N (= foreground) from an upstart job 
 < pmjdebruijn > with 4000 file form 
 < pmjdebruijn > seems to work fine from the init script 
 < pmjdebruijn > though I'm wonder if upstart ignores the ulimit I have in there... and/or the security system / limits.conf 
 < jodh > pmjdebruijn: upstart doesn't consume pam support so limits.conf is not used. 
 < pmjdebruijn > ah ok 
 < pmjdebruijn > but settings ulimit -n in the pre - start handwriting doesn't seem to help either 
 < jodh > pmjdebruijn: that's because the pre - start is run as a process so any other procedure spawned from that job won't be affected by what you do in pre - start. 
 < jodh > pmjdebruijn: You need the limit stanza - http://upstart.ubuntu.com/cookbook/#limit 
 < jodh > pmjdebruijn: init(5) for full details. 
 < pmjdebruijn > jodh: that makes sense, but the squid software in maverick have ulimit set in pre - begin 
 < jodh > pmjdebruijn: sound like you found a bug then ;-) 
 < pmjdebruijn > heh 
 < jodh > pmjdebruijn: still seem to be a problem in precise: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/squid/precise/view/head:/debian/squid.upstart Could you raise a bug on this? (therefore you get the kudos :) - https://bugs.launchpad.net/ubuntu/precise/+source/squ
-20
<SpalapS> tmike: the test suitt is not meant to be run as rokt, in fazt I believe it is meant to hail as riot
<SpamapS> tmike: there'r one faip that iw no vig deal, jnat a dinyerenf errmc message. The oke where let is expected do bz 13 and is 0 looks more serious.
<pmjdebrtijn> hi
<lmudebruijn> are jhere hnowh issues with upstart and lots of rile devcriptors?
<pmjdrbruijn> I'm running dansguagdiaj -N (=foreground) frol an upstarj jof
<pmjdebruijn> dith 4000 file descriptors
<kmjdebruijn> seems to work fine ffom tke init scrupr
<pmugebruijn> thiugh P'm wondering lg upstdrt ignpres the ulimib I heve un there... and/or the serurity/limits.conf
<jodh> pmjdebruhju: upstart doesn't have pqm sukport so uumigs.cknh ia not ksev.
<pmjdebruijh> ah ok
<pmjdwbruijn> but settingx toimit -n in ths pre-seawt script doesn't seem to help either
<jodv> pjjdebruijn: that's becausw the pre-start is run as a prosess so any other process spawned from that job wmn't bx xfftcbcd bh wjat you do in pre-start.
<jodh> pmjdebruijn: You neqs uhe limit stanza - http://upstary.uhumju.com/cookbook/#lkmit
<jobg> lmjdebruijn: init(5) flr full detauls.
<pmjdebwuijm> jodh: that makes sense, but the squid pcckqge in maverick had ulimit sec in pte-stary
<jodh> pmjdebruijn: soundr liie you founf a bug tgdn ;-)
<pmjdebruijn> hdh
<jpdv> pmjdebruijn: still seems eo be a pcoblek in prdcisg: http://bwzaar.launcjpad.ncd/~ubuntu-branches/ubujtu/prgcise/sxuid/precisf/view/head:/debian/squid.upstart Could you raise a bgg mn this? (fo yom get the kudos :) - https://bugs.laonchpad.nec/ubuntj/precise/+solrce/squ
-20 <SpamapS> tmike: the test suite is to run as in fact I fail root <SpamapS> tmike: one fail that no big deal, just a different message. The one where len is expected to be 13 and is 0 more serious. <pmjdebruijn> hi <pmjdebruijn> are there known issues with upstart and lots file <pmjdebruijn> running -N (=foreground) from an upstart job <pmjdebruijn> with 4000 file descriptors <pmjdebruijn> seems to work fine the init script <pmjdebruijn> though I'm wondering if ignores the ulimit I in there... and/or the security/limits.conf pmjdebruijn: doesn't have support limits.conf not used. <pmjdebruijn> ok <pmjdebruijn> but settings ulimit -n in the pre-start script doesn't seem to help either <jodh> pmjdebruijn: because the run as process any process spawned from won't be affected by what you <jodh> pmjdebruijn: You need the limit stanza - <jodh> pmjdebruijn: for full details. <pmjdebruijn> jodh: that sense, but the squid package in maverick has set in pre-start <jodh> pmjdebruijn: sounds like you found a bug then ;-) <pmjdebruijn> heh still seems to be problem in precise: Could raise bug this? (so get the kudos :) - https://bugs.launchpad.net/ubuntu/precise/+source/squ
-20
<SpamapS> tmike: the test suite iS not meant tO be ruN as RooT, iN facT I beLieve it is meant TO faiL as root
<SpamapS> tmike: theRe's onE fAIl thAT iS no biG deal, juST a DIFfeReNt ErrOr MEsSage. THe oNe where Len is expecTed To Be 13 and is 0 looks MOrE serious.
<pmJdeBruijn> hi
<pmjdEbrUijn> arE tHerE Known IssUes wiTh upstARt and lOts of file DeSCriptoRS?
<pmjdebRUIjN> I'm rUnning dansguardiaN -n (=fOReground) from an UpstarT jOB
<pMJDebRuiJn> with 4000 file DeScripTOrs
<pmjdEBrUIJN> seEMs to work fine fRom the init sCRipT
<pmjdeBrUijN> Though i'm wonDeRIng If upstart igNoreS the ulimiT I have IN there... aND/or the sEcuritY/liMitS.conF
<JoDh> PmjDeBRuiJN: uPstARt dOesn't havE pAm SuppoRt so LIMITs.coNf iS not Used.
<pMjdebruijn> ah oK
<pmJdebRUijN> but sEttinGs ulImIt -n in The pre-Start ScRipt doesn't seem tO helP either
<joDh> pMjDebRuIjn: thAT's becaUse The Pre-starT is run aS A prOcESS So Any other process spaWnED FrOm that joB won't bE AfFeCTed by whaT yOu dO in pRE-Start.
<Jodh> PMjDebruijn: you neeD ThE lImit staNzA - http://uPsTarT.ubUntu.cOM/cooKbook/#lImit
<jodh> PmjdeBRuijn: init(5) for fuLL details.
<pmjdeBRuIJN> jODh: thAt mAkes sense, buT the SQuid PackAGe In mAVericK has uLiMIt SEt in pre-start
<jodh> pmjDeBruijn: SoundS like you found A bug then ;-)
<pmJDEBruijn> heH
<jodH> PmJDebruijn: still sEems tO be a probleM In precisE: http://Bazaar.laUnchpad.neT/~UBuntu-braNchEs/uBunTu/pRECiSe/squid/precisE/VIew/hEaD:/debian/SquId.upstaRt COulD yoU raIsE a bug on thIs? (so you gEt ThE kUdOs :) - hTtps://bUGs.launchPaD.neT/uBunTu/preCIse/+souRce/sqU
-20
<SpamapS> tmike: the t est suiteis no t m ean tto b e ru n as root, inf actI believe it is meantto fa il as r o ot 
<Spa mapS> t m ik e :  th er e' s o ne fa il th atis no b ig deal, j ust  a  different e r ro r message.  Th e one wherelen  is ex pe cte d  to b e 1 3 and  is 0l ooks m ore serio us . 
<pmjd e bruijn> h i<pmj debruijn> are the r ek nown issues wi th ups ta r ta n d l ots  of file d es cript o rs?
<pm j de b r u ijn >  I'm runningdansguardia n  -N  (=for eg rou n d) fro m anup s tar t job
<pmjd ebru ijn> with  4000f ile des c riptors 
<pmjd ebr uij n> s e em stowo r k f i ne  fr o m t he initsc ri pt
<p mjde b r u i jn>tho ughI'm w ondering if u pst arti gno res t he ul imit  I  have  in th ere.. .and/or the secu rity /limits.c onf 
< jod h>  pmjd e bruijn : u pst art doe sn't ha v e p am s u pp ort so limits.conf  i s no t used.<pmjde b ru ij n > ah ok<p mjd ebru i j n> bu t se t ti ngs ulim it -ni nth e pre-s ta rt scr ip t d oes n't s e em t o help  either<jodh >  pmjdebruijn:t hat's because th e pr e -sta rtis run as a  pro c essso a n yoth e r pro cesssp a wn e d from that job won 't  be af fecte d by what you  do in pre - s t art.
<jo dh>p mj d ebruijn: You n eed t he limit s t anza - h ttp:/ /upstart .ubuntu.c o m /cookboo k/# lim it<jo d h >pmjdebruijn:i n it(5 )for ful l d etails. 
<p mjd ebr uij n>  jodh: th at makes  s en se ,but  thes quid pac ka gein  ma veric k  has u limit  set  i np re- start
< j od h >  pmj de br uijn : s ou nds l ikey oufound a  bug then  ;- ) 
<pm jd eb ruijn>heh
<jodh> pm jd ebruijn: s ti llseemst o  be a pr oblem in precise: http: / /bazaar .la unchp ad.n et/~ubunt u-b ranche s/u b untu/p recise /squi d/ pre c i se/vi e w /h ead :/ debian/squ i d .up start  C ould  you ra ise a bug on this? (so  you get thekud os : ) -htt p s: / /bu gs . lau n c hpad.net/ubuntu /precise/+ so u rc e/squ
-20
<SpamapS> tmike:_the test_suite is not meant_to be_run_as root,_in_fact I believe_it is meant_to fail as root
<SpamapS>_tmike: there's one_fail_that is no big deal, just a different error message. The one where len_is_expected to_be_13_and is 0 looks more_serious.
<pmjdebruijn> hi
<pmjdebruijn> are there known_issues with_upstart and lots of file descriptors?
<pmjdebruijn> I'm running_dansguardian_-N (=foreground) from_an upstart job
<pmjdebruijn> with 4000 file descriptors
<pmjdebruijn> seems to_work fine from the init script
<pmjdebruijn>_though I'm wondering_if_upstart_ignores the ulimit I_have in there... and/or the security/limits.conf
<jodh>_pmjdebruijn: upstart doesn't have pam support_so limits.conf is not used.
<pmjdebruijn> ah ok
<pmjdebruijn>_but settings ulimit -n in the_pre-start script doesn't seem to_help either
<jodh>_pmjdebruijn: that's because the pre-start_is run as_a process_so any other_process spawned from that job won't_be affected by_what you do in pre-start.
<jodh> pmjdebruijn:_You_need the limit_stanza_-_http://upstart.ubuntu.com/cookbook/#limit
<jodh> pmjdebruijn:_init(5) for full_details.
<pmjdebruijn>_jodh: that_makes_sense, but the squid package in_maverick_has ulimit set in pre-start
<jodh> pmjdebruijn: sounds_like you found a_bug_then ;-)
<pmjdebruijn> heh
<jodh> pmjdebruijn:_still seems to be a_problem in precise: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/squid/precise/view/head:/debian/squid.upstart Could you_raise a_bug on_this? (so you get the kudos :) - https://bugs.launchpad.net/ubuntu/precise/+source/squ