Re: Getting a core dump from Varnish 1.1.2

2008-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Nath an Kinkade" writes: >Child said (2, 13865):

varnish uptime

2008-07-24 Thread Olivier Beau
Hi all, Is there a way in varnish to get the child's uptime ? (otherwise i'll get it with a 'ps'..) Olivier Beau ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc

Re: varnish uptime

2008-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Olivier Beau writes: > >Hi all, > >Is there a way in varnish to get the child's uptime ? >(otherwise i'll get it with a 'ps'..) It's at the top left corner of varnishstat output -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TC

Re: varnish uptime

2008-07-24 Thread Olivier Beau
> >Is there a way in varnish to get the child's uptime ? > >(otherwise i'll get it with a 'ps'..) > > It's at the top left corner of varnishstat output yes i saw, but i'ld like to get it in my monitoring script shell; and it's not available in varnishstat -1 Olivier __

Re: Getting a core dump from Varnish 1.1.2

2008-07-24 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Nath an Kinkade" writes: >> Alternatively, try to update to a -trunk version, it's much better >> than 1.1.2. > > >Is there a particular revision number in trunk that is worth grabbing, >or is it presumed that HEAD is stable enough for a fairly busy >production mac

Re: Getting a core dump from Varnish 1.1.2

2008-07-24 Thread Nathan Kinkade
2008/7/24 Poul-Henning Kamp <[EMAIL PROTECTED]>: > In message <[EMAIL PROTECTED]>, "Nath > an Kinkade" writes: > >>Child said (2, 13865): < > I belive this message means that you run out of workspace somewhere, > but I can't remember the details for 1.1.2 any more. > > Try increasing the session wo

Re: Getting a core dump from Varnish 1.1.2

2008-07-24 Thread Nathan Kinkade
2008/7/24 Poul-Henning Kamp <[EMAIL PROTECTED]>: > In message <[EMAIL PROTECTED]>, "Nath > an Kinkade" writes: > >>> Alternatively, try to update to a -trunk version, it's much better >>> than 1.1.2. >> >> >>Is there a particular revision number in trunk that is worth grabbing, >>or is it presumed