Hello
Attached is an email , documenting the exact problem
I'm experiencing now.
The machine is running 3.4 Stable. It's a fairly busy
shell server with all the standard toys.
In short , ps -a ... or ps -u fails with no error , and
is not able to be killed , and exists in a
On Thu, Sep 28, 2000 at 07:10:10PM +0900, Makoto MATSUSHITA wrote:
But wait, wait a minute...
If you wanna say "make release", you already know about that an
exciting, cool, and misterious world is there. Why not adding
vn_load="YES" to your loader.conf and reboot ?
1. No one has
Is it painless to do this upgrade? The UPDATING file is very small and
contains almost nothing.
I've gotten so used to the `make build/installkernel` in 4.1-STABLE.
This is not implemented in the 3-branch, or?
--
__o
regards, Gunnar ---_ \,_
email: [EMAIL
On Fri, 29 Sep 2000, Gunnar Flygt wrote:
| Is it painless to do this upgrade? The UPDATING file is very small and
| contains almost nothing.
|
| I've gotten so used to the `make build/installkernel` in 4.1-STABLE.
| This is not implemented in the 3-branch, or?
It's a stroll in the park, just
On Thu, Sep 28, 2000 at 03:11:19PM -0700, Tom wrote:
On Thu, 28 Sep 2000, Jared Chenkin wrote:
I'm having some space problems on my FreeBSD 3.3-STABLE box.
The problem is that the previous administrator did not give
me alot of space on the root partition, and now its at 95%
and
FreeBSD-4.1.1 distribution has a useful script meant for
enforced fetch of mail from secondary mx-servers:
/usr/src/contrib/sendmail/contrib/etrn.pl
It begins with a line "#!/usr/local/bin/perl",
while default location of perl here seems to be /usr/bin/perl.
Without correcting it, script just
Hello,
I noticed some strange behavior in pthreads applications,
close on socket which is in accept() will be blocked untill there's a connection
to port and accept returns.
It's observed on 4.0 - 4.1-STABLE, perhaps 4.1.1-STABLE as well, but I didn't
try it. I don't have 3.5.1-STABLE system to
* Roman Shterenzon [EMAIL PROTECTED] [000929 01:23] wrote:
Hello,
I noticed some strange behavior in pthreads applications,
close on socket which is in accept() will be blocked untill there's a connection
to port and accept returns.
It's observed on 4.0 - 4.1-STABLE, perhaps 4.1.1-STABLE as
Quoting Alfred Perlstein [EMAIL PROTECTED]:
I attach example program, which, when receives SIGUSR1 should close
the socket,
but, in fact gets blocked in the close() function.
Obviously it's waiting to acquire some lock.
Does anyone have an idea?
Yes, I have an idea and an idea how to
I own a couple of the PowerWare Prestige 1500VA units with extra
external battery packs, and have some documentation. Running a
FreeBSD system, a Windows98 box, my cable modem and NAT/Firewall
gets me about an hour of keep-alive.
The serial port on the back can be kicked into several different
* Roman Shterenzon [EMAIL PROTECTED] [000929 01:52] wrote:
Quoting Alfred Perlstein [EMAIL PROTECTED]:
I attach example program, which, when receives SIGUSR1 should close
the socket,
but, in fact gets blocked in the close() function.
Obviously it's waiting to acquire some lock.
11 matches
Mail list logo
