I'm not sure I understand the question - but I'll give it a go... There are many situations which spawn a new thread, which can happen at any time during the server's life span. Certain core server functionality use pools of threads where new threads are spawned the first time they are needed (but only when existing available ones are already in use)
For example, - connection threads above "minthreads" (up to "maxthreads") - calls to ns_thread -begindetached or ns_job (ns_eval does this) - calls to ns_schedule_proc -thread You could also issue the aolserver "ns_info threads" command if you are curious as to the purpose of the various threads. Does this answer your question or did I misunderstand? -Elizabeth Bernd Eidenschink wrote on 2/18/04, 7:09 AM: > Hi, > > below is what I get on one of my servers, running ps (I shortened > "COMMAND" to make it readable). > This is from AOLserver series 3. I don't know exactly how to interpret > "TIME", especially when looking at "START". > > Sure, after a (configurable) while (or when using ns_eval), one or more > threads are re-started (explaining the wide PID-differences), but, > especially as I use ns_eval very often for some API's, it does not > explain the gaps of the "START" column. > > How to read this? Thanks! > > Bernd. > > -------------- > > # ps -afx -o user,pid,ppid,start_time,time,command > > PID PPID START TIME COMMAND > 22181 1 Feb05 00:01:28 [...]/nsd -izt [...]/c.cfg [-u / -g] > 22184 22181 Feb05 00:00:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 22185 22184 Feb05 00:00:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 22186 22184 Feb05 00:03:45 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 22191 22184 Feb05 00:00:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 22192 22184 Feb05 00:08:43 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 22195 22184 Feb05 00:03:15 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 16197 22184 Feb14 01:03:42 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 20454 22184 Feb14 00:53:41 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 24594 22184 Feb14 00:47:37 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 29495 22184 Feb15 00:43:17 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 30635 22184 Feb15 00:54:57 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 32514 22184 Feb15 00:38:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 9750 22184 Feb16 00:23:25 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 10646 22184 Feb16 00:21:26 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 10682 22184 Feb16 00:22:09 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 10977 22184 Feb16 00:21:06 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 12620 22184 Feb16 00:19:40 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 12621 22184 Feb16 00:20:12 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > 30210 22184 Feb17 00:05:05 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
