From owner-freebsd-current Sat Sep 12 14:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13503 for freebsd-current-outgoing; Sat, 12 Sep 1998 14:18:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13479 for ; Sat, 12 Sep 1998 14:18:40 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id XAA02672; Sat, 12 Sep 1998 23:14:43 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id XAA28964; Sat, 12 Sep 1998 23:12:39 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199809122112.XAA28964@semyam.dinoco.de> To: Edwin Culp cc: Cyrus Rahman , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: updatedb ? In-reply-to: Your message of "Sat, 12 Sep 1998 10:12:32 CDT." <35FA8F60.25F651F@webwizard.org.mx> Date: Sat, 12 Sep 1998 23:12:38 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I changed the #!/bin/sh to #!/usr/local/bin/ksh and it seems to work fine, > although I still don't understand why the problem with sh. The change from 1.22 to 1.23 in parser.c of /bin/sh seems to cause this malfunction. I removed it, recompiled sh, installed it and then called 310.locate manually. Now it worked for me. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message