Return to BSD News archive
Xref: sserve comp.unix.bsd:15080 comp.os.386bsd.bugs:2572 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.moneng.mei.com!howland.reston.ans.net!swiss.ans.net!cmcl2!newsserv.cs.sunysb.edu!starkhome.cs.sunysb.edu!localhost!gene From: gene@starkhome.cs.sunysb.edu (Gene Stark) Newsgroups: comp.unix.bsd,comp.os.386bsd.bugs Subject: Re: Start date of all procs 1 Jan 1970 ( FreeBSD 1.1.5.1) Date: 13 Oct 94 09:28:21 Organization: Gene Stark's home system Lines: 18 Message-ID: <GENE.94Oct13092821@starkhome.cs.sunysb.edu> References: <CxKHH0.1y8@olivetti.nl> NNTP-Posting-Host: localhost.cs.sunysb.edu. In-reply-to: paulz@olivetti.nl's message of Wed, 12 Oct 1994 15:53:24 GMT >On a 386 box I'm running all procs always have a 1 Jan 1970 start date, >same for the times in /proc. >It looks like the time struct in the kernel is not being updated. >Can someone point me the location in the sources where that should >be done?? >Or even better can some tell me the cause of this behaviour ?? Is the name of the kernel you are running "/386bsd"? Has "kvm_mkdb" run properly on bootup to create the kernel symbol database? Have you got /proc mounted properly. Do /dev/mem and /dev/kmem exist, and do they have permissions such that a process running "ps" can read them? The problem you describe will occur if ps is unable to find the start time information in the kernel it requires, and therefore uses the value 0 instead. I am fairly certain that the time is getting updated properly, it's just that ps can't find it. - Gene Stark