The changes that I added to soft updates two days ago only kick in
when the soft dependency memory limit is hit. This certainly should
not be happening at system startup, and on any machine with more
than 64Mb of memory, almost never. I did make a couple of minor
textual changes to other parts of the code which should not have
had any effect, but just in case they did, I have put them back to
their previous state in today's delta. I would appreciate your
trying out the current delta (1.27) and seeing if the problem
persists. If it does, please try out the version before I did my
recent rework (1.24). If that version has the problem as well, then
I believe that some other change is triggering the problem, as 1.24
represents a version that has been in production for half a year
without trouble.
Kirk McKusick
=-=-=-=-=-=-=-=
Date: Sun, 9 May 1999 01:39:33 -0700 (PDT)
From: Julian Elischer <jul...@whistle.com>
To: mckus...@mckusick.com
Subject: Re: Disappearing/Reappearing Files... (fwd)
FYI
also some other people are commenting on odd behaviour where a created
file doesn't show up for a while...
almost as if the readdir() is returning the 'backed out' version of the
directory data.
julian
---------- Forwarded message ----------
Date: Sat, 8 May 1999 14:11:10 -0700 (PDT)
From: John Polstra <j...@polstra.com>
To: curr...@freebsd.org
Subject: Re: Disappearing/Reappearing Files...
In article <199905082048.naa34...@vashon.polstra.com>,
John Polstra <j...@polstra.com> wrote:
>
> I'm seeing something possibly related (possibly not) on an Alpha with
> this morning's -current. First I was getting unaligned accesses and
> core dumps from the "cp" in /etc/rc that updates the /etc/motd file.
> (I added "set -v" to /etc/rc to catch it.) But I could do the copy by
> hand once the system was up. Now on the latest reboot I got this from
> it:
>
> + cp /tmp/_motd /etc/motd
> + chmod 644 /etc/motd
> chmod: : No such file or directory
> chmod in free(): warning: recursive call
> chmod in free(): warning: recursive call
> chmod in free(): warning: recursive call
> chmod in free(): warning: recursive call
>
> (Hmm, why didn't the filename come out in chmod's error message?)
>
> I'm running with soft-updates but I'll try turning them off.
I tried about 10 reboots, half with and half without soft-updates
enabled on the various filesystems. With soft-updates disabled, I
didn't see the above problem at all. With soft-updates enabled, I saw
it most of the time but not always.
John
--
John Polstra j...@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-interest is the aphrodisiac of belief." -- James V. DeLong
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
