libkvm sucks

1999-05-17 Thread Marc Slemko
The premise: libkvm is fatally flawed by design, and fixing it is not an easy proposition. The reasoning: reading from kernel data structures without any locking has obvious race conditions. This is why any identd that uses libkvm sucks and gets into loops all the time, etc. This is why netst

Re: so use sysctl (was: Re: libkvm sucks)

1999-05-17 Thread Marc Slemko
On Tue, 18 May 1999, Alfred Perlstein wrote: [...] > unf! > > part of a multithreaded ident server that i got bored with... > i'm not entirely sure it still works: Yea, that idea works, thanks. I didn't notice that the way this is done was changed in 3.x to add the sysctl option. I do wonde

Re: libkvm sucks

1999-05-18 Thread Marc Slemko
On Tue, 18 May 1999, Richard Wackerbarth wrote: > On Mon, 17 May 1999, Marc Slemko wrote: > > > The reasoning: reading from kernel data structures without any locking has > > obvious race conditions. > [...] > > > This is why netstat will often bail out in t

Re: a.out behavior

1999-06-06 Thread Marc Slemko
On Sun, 6 Jun 1999, Marc Tardif wrote: > The following code should obviously segfault: Nope. There is no requirement that code segfault. C does not make any promises that accessing memory that you have not allocated will do anything. > #include > #include > > char buffer[4028]; > > void ma

MAXPATHLEN not enforced

1999-10-16 Thread Marc Slemko
Why does FreeBSD let you create paths longer than MAXPATHLEN? I often have various trees that are as deep as possible for testing various programs for holes, and I finally figured out why locate wasn't updating its database properly; it was choking as soon as it saw a path length >MAXPATHLEN l