Actually, what I suspect is happening, is that the maxfiles is raised for
all future processes spawned by init (or what have you), but /etc/rc's
shell is already running and all the descendents of that shell inherit the
same rlimits as their parent. Thus, it seems to make sense as to why your
ircd
"Thomas T. Veldhouse" wrote:
>
> Is the next FreeBSD release going to be numbered 4.4? Now won't that be
> confusing to newcomers :)
>
Wasnt there a bsd4.3 and 4.2 so isnt it already confusing
--
Simon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in
> >Maybe I'm missing something.. why would it be confusing?
Christopher Schulte <[EMAIL PROTECTED]> writes:
> 'A complete operating system based on 4.4BSD.'
Not as silly as the inevitable stupidity: Pentium 5.
:-) / 2
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-st
The box is a dual P3 with 2g ram, running Qmail which is handling inbound
email. I'm running 4.2 Release (though I've had similar problems with 3.4
Stable a few months back, and never solved them either).
After a 36 - 48hrs, the box will panic with "panic: pipeinit: cannot
allocate pipe -- out of
:: No, the behavior should stay the same by default, with a flag that can be
:: used to turn on "sanity checking". You would have to change FAR, FAR too
:: many things to make the whole system dafault to "typo proof" behavior.
::
:: Like I said in my previous message, having some sort of add-on t
On Tue, 1 May 2001, Juha Saarinen wrote:
> Note the "rare situations" -- it's not useful when you make a typo, or a
> mistake.
>
> :: Remember, a directory is treated as a
> :: regular file on unix filesystems.
>
> Not sure about this; if you e.g. vi a directory, it will warn you that it
> isn
Arthur W. Neilson III writes:
This very functionality, being able to cat a directory, saved my butt
some years ago on an unfamiliar sys5r2 box which had crashed and no
filesystem but root would mount. ls wasn't in the path and I
remembered I could use cat
On Mon, 30 Apr 2001, Chris Byrnes wrote:
> > It might be, depending on what you were feeding it to. I think the
> > point people are making is that directory data is, in certain cases,
> > also potentially useful for something they might conceivably want to
> > do, and if you yourself don't want
> "Juha" == Juha Saarinen <[EMAIL PROTECTED]> writes:
Juha> Note the "rare situations" -- it's not useful when you make
Juha> a typo, or a mistake.
A better fix would be to change your shell to /usr/local/bin/ispell.
Juha> So the best thing to do is to keep the current behaviour
> "Donn" == Donn Miller <[EMAIL PROTECTED]> writes:
Donn> Yeah, and you can do cat dirname | strings;
Another recipient of the Gratuitous Use of Cat award. 'strings dirname'
works just fine. (And if he didn't have ls available, it's a safe bet
that strings wasn't there, either ;-)
--lyn
I was going to let this one go, but...
:: Like so many people before you already explained, doing tail on a
:: directory IS useful in some rare situations, like for example, using
:: tar, and certain other things.
Note the "rare situations" -- it's not useful when you make a typo, or a
mistake.
On Tue, May 01, 2001 at 03:23:15AM -0600, Doug Russell wrote:
>
> You could then put your machine in "user friendly" mode if desired, but
> those of us who expect Unix to behave like Unix can set it to mode
> 0. There could be levels in between without the "Are you sure you are
> really sure you
"Thomas T. Veldhouse" wrote:
>
> Sounds like hardware to me. You probably want to run a time program via
> cron to periodically update the clock rate.
Well, that may be, but it was pretty well-behaved hardware until I used
plip--no clock drift whatsoever. I have the daemon running at boot to
u
13 matches
Mail list logo
