From owner-freebsd-questions Mon May 15 5:49:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id BD47437B6B9 for ; Mon, 15 May 2000 05:49:39 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id IAA12250; Mon, 15 May 2000 08:50:20 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000515084318.00ac5ee0@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 15 May 2000 08:53:08 -0400 To: Ben Smithurst From: John Subject: Re: locate database disappears Cc: freebsd-questions@freebsd.org In-Reply-To: <20000515075537.U10128@strontium.scientia.demon.co.uk> References: <4.3.1.2.20000515000015.00ac5100@mail.udel.edu> <4.3.1.2.20000515000015.00ac5100@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've finally managed to trace this back to being "caused" by > > /etc/periodic/weekly/310.locate, which I've pasted below (it's the > standard > > plain-old version that was installed during a make world - I haven't > > modified it at all). I've yet to figure out *why* though? Any > > thoughts? I'm running 3.4-stable now, and this problem didn't come into > > being until I had upgraded from 3.3-stable to 3.4-stable. > > > > cd / > > echo /usr/libexec/locate.updatedb | nice -5 su -fm nobody > >Have you tried running those commands manually? Perhaps there's a >problem with running it as the "nobody" user somewhere. Oops... didn't think of trying that... the, however, was no error message, and again a small database. >If you run those and it get's set to 500 bytes again, without an error >message, >try: > >| cd / >| echo /usr/libexec/locate.updatedb | nice -5 ktrace -i su -fm nobody > >and then > >| kdump | less (or kdump | more, whatever) > >scroll to the end, see if you can see any errors occuring. Well, I can't try this immediately - I don't have the KTRACE option in my current kernel. I can recompile it tomorrow night to give it a shot. Any chance of an alternate troubleshooting method for now? Thanks!!! --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message