From owner-freebsd-questions Wed Jun 5 19:30:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA25665 for questions-outgoing; Wed, 5 Jun 1996 19:30:10 -0700 (PDT) Received: from bambi.pomona.edu (bambi.pomona.edu [134.173.64.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA25656 for ; Wed, 5 Jun 1996 19:30:06 -0700 (PDT) Received: from POMONA.EDU by POMONA.EDU (PMDF V5.0-7 #12356) id <01I5K799JP9C8WYJ13@POMONA.EDU> for questions@freebsd.org; Wed, 05 Jun 1996 19:29:06 -0800 (PST) Date: Wed, 05 Jun 1996 19:29:06 -0800 (PST) From: JOHN Subject: 31Dec69? - date for tcsh process To: questions@freebsd.org Message-id: <01I5K799LGDE8WYJ13@POMONA.EDU> X-VMS-To: IN%"questions@freebsd.org" MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed recently that an output of ps aux shows that my tcsh process has a status of having been started on the 31 Dec 69, and this is always while forking. (STAT = RV) I'm assuming the date is due to the forking process, and the clock has not been "synchronized" for that process? I'm not the most knowledgeable when it comes to Unix internals. Will this happen with all processes caught by ps aux whilst forking, or is it some peculiar tcsh quirk? I'm assuming that the tcsh process is forking due to the call of ps? Just curious, John