I have a dedicated syslog machine runnign 3.2 and vanilla syslogd
(started with -vv flags). After running for a few day the file would grow
(this time file was ~40MB) and syslogd would stop writing to a file and
go into a weird state. Here is the ktrace of "hang" syslogd before I did
'reboo
I have a dedicated syslog machine runnign 3.2 and vanilla syslogd
(started with -vv flags). After running for a few day the file would grow
(this time file was ~40MB) and syslogd would stop writing to a file and
go into a weird state. Here is the ktrace of "hang" syslogd before I did
'rebo
On Fri, Jul 30, 1999 at 08:58:09PM -0700, "Jordan K. Hubbard"
wrote:
> http://features.linuxtoday.com/stories/8191.html
>
> A story on upcoming plans for the Linux 2.4 kernel. Since they're
> going after a lot of the same performance goals we are, it's worth a
> read.
>
> - Jordan
>
>
> To U
On Fri, Jul 30, 1999 at 08:58:09PM -0700, "Jordan K. Hubbard" <[EMAIL PROTECTED]>
wrote:
> http://features.linuxtoday.com/stories/8191.html
>
> A story on upcoming plans for the Linux 2.4 kernel. Since they're
> going after a lot of the same performance goals we are, it's worth a
> read.
>
> -
On Sun, Jul 25, 1999 at 11:36:49AM -0700, Matthew Dillon
wrote:
> A sandbox is a security term. It can mean two things:
>
[...]
>
> UNIX implements two core sanboxes. One is at the process level, and one
> is at the userid level.
>
> Every UNIX process is completely firewalle
On Sun, Jul 25, 1999 at 11:36:49AM -0700, Matthew Dillon <[EMAIL PROTECTED]>
wrote:
> A sandbox is a security term. It can mean two things:
>
[...]
>
> UNIX implements two core sanboxes. One is at the process level, and one
> is at the userid level.
>
> Every UNIX process is
6 matches
Mail list logo
