--- Alexander Barkov <[EMAIL PROTECTED]> wrote:
> Caffeinate The World wrote:
> >
> > --- Alexander Barkov <[EMAIL PROTECTED]> wrote:
> > > Caffeinate The World wrote:
> > > >
> > > > 3.1.12-cvs
> > > >
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/118.htm
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/135.htm
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/161.htm
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/167.htm
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/182.htm
> > > > [1] http://www.state.mn.us/archive/ctapun/9806/214.htm
> > > > ^^^
> > > > \_ that used to be the PID of the indexer process. now
> > > > it always shows 1.
> > > >
> > >
> > >
> > > It is thread id, not pid.
> > did this behavior changed? because back in 3.1.10 that number
> always
> > matched my PID for that process. i don't have thread enabled.
> >
>
>
> It always displays thread id, never pid.
>
> You can see pid in syslog, but not in indexer output to stderr.
that's quite strange as i've seen only PID. the only thing i did
different was disable syslog for 3.1.12. before that, i've always had
it. i used to kill indexer just by using those #s since they've always
matched PID. anyway, i was just curious.
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
___________________________________________
If you want to unsubscribe send "unsubscribe general"
to [EMAIL PROTECTED]
