Wait - so there's an issue that you have identified, with help from
members on this list ? And you're refusing to divulge the exact
details that would probably help resolve the problem in future OpenBSD
releases ?
What the hell.
That's a great thank you to all those people that helped you, Lee,
especially the ones you don't mention by name here below. Just great.
Good that you have at least taken the time and effort to make us
reread your own little flame (in all caps, because that helps so much
to bring the message across).
Paul 'WEiRD' de Weerd
PS: Best part ? "MOST LIKELY"
On Wed, Jan 18, 2012 at 10:15:34AM -0600, L. V. Lammert wrote:
| It was truly a shame that so many people here prefer to start their
| flamethrowers rather than offer any sort of constructive
| information! In this case, THE PROBLEM HAS BEEN IDENTIFIED AND IT
| WOULD MOST LIKELY NOT HAVE BEEN FIXED WITH A NORMAL UPGRADE! !! !!!
| !!!!
|
| Before reading further, please REREAD the statement above.
|
| As it turns out, there WERE some folks here that had excellent
| suggestions [privately], and that helped significantly in isolating
| the problem. Thanks to ____ who got me back on topic and reminded me
| of this possible issue, .. and ____ who suggested the simplest
| solution:
|
| find / ! \( -fstype ffs -or -fstype ufs -or -fstype ext2fs \) -prune
| -or -path /tmp -prune -or -path /var/tmp -prune -or -path /usr/tmp
| -prune -or -print > /tmp/locate test
|
| Running the find separately identified the file system problem, and
| it was easily fixed as a result.
|
| Lee
|
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
