Joesh Juphland wrote:
You wouldn't happen to have a portmap_enable=NO line in your rc.conf,
would you?
No, I do not. Further, I see 'portmap' in the process list, so it is indeed
running.
ipfw add 1 allow all from any to any
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Fri, Oct 26, 2001 at 09:15:28AM +0200, Peter Wullinger wrote:
Err ... just another dump question:
I'm unable to access the anoncvs server ...
(using bash)
% export CVSROOT=:pserver:[EMAIL PROTECTED]:/home/ncvs
% cvs login
(Logging in to [EMAIL PROTECTED])
CVS password:
In some email I received from Giorgos Keramidas, sie wrote:
On Tue, Oct 23, 2001 at 07:45:11PM +0200, Gerhard Sittig wrote:
I get the feeling this - inappropriate - setting of a _program
variable is due to my misguided suggestion in PR conf/20202
which verbatimly made it into the FreeBSD
On Thu, 25 Oct 2001, Terry Lambert wrote:
To do what you want, which is to clean the backing pages, you
Yes, i mean cleaning pages in the backing storage.
are better off doing it for all freed blocks, not just swap
blocks (if someone can read your swap, they can read other data
off your
In article [EMAIL PROTECTED] you write:
How many of the patches at http://labs.gr/~charon/patches/ should go into
FreeBSD-current ?
Darren
I wrote similar patches (see http://home.iae.nl/users/devet/freebsd/)
trying to fix more or less the same bugs/problems.
Maybe it's a good idea if Giorgos
ok if you into your freebsd box from somewhere else and type su - root and
then type the root password it just hangs there and you think I'm sure I
typed the password correctly.
So then you u think ok the the SSH session died for some reason try to log
back in via ssh and you can't and when you
Ian Dowse wrote:
In message [EMAIL PROTECTED], Maxim Sobolev writ
es:
Nautilus from working properly. The problem disappeared when I've replaced
writev(2) call with appropriate loop based around ordinary write(2). Perhaps
this should be investigated and the real source of the problem
On Fri, Oct 26, 2001 at 05:49:08PM +0300, Maxim Sobolev wrote:
Ian Dowse wrote:
In message [EMAIL PROTECTED], Maxim Sobolev writ
es:
Nautilus from working properly. The problem disappeared when I've replaced
writev(2) call with appropriate loop based around ordinary write(2).
On Fri, Oct 26, 2001 at 09:21:37PM +1000, Darren Reed wrote:
In some email I received from Arjan de Vet, sie wrote:
In article [EMAIL PROTECTED] you write:
How many of the patches at http://labs.gr/~charon/patches/ should go into
FreeBSD-current ?
I wrote similar patches (see
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 05:49:08PM +0300, Maxim Sobolev wrote:
Ian Dowse wrote:
In message [EMAIL PROTECTED], Maxim Sobolev writ
es:
Nautilus from working properly. The problem disappeared when I've replaced
writev(2) call with appropriate loop based
On Fri, Oct 26, 2001 at 06:06:59PM +0300, Maxim Sobolev wrote:
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 05:49:08PM +0300, Maxim Sobolev wrote:
[snip]
On the step 3, when marshalling results of the call, daemon
creates a large collection of small buffers (usually 5-10
bytes
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 06:06:59PM +0300, Maxim Sobolev wrote:
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 05:49:08PM +0300, Maxim Sobolev wrote:
[snip]
On the step 3, when marshalling results of the call, daemon
creates a large collection of small
On Fri, Oct 26, 2001 at 06:31:56PM +0300, Maxim Sobolev wrote:
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 06:06:59PM +0300, Maxim Sobolev wrote:
Peter Pentchev wrote:
On Fri, Oct 26, 2001 at 05:49:08PM +0300, Maxim Sobolev wrote:
[snip]
On the step 3, when
On Fri, Oct 26, 2001 at 12:46:00PM +0100, Bri wrote:
ok if you into your freebsd box from somewhere else and type su - root and
then type the root password it just hangs there and you think I'm sure I
typed the password correctly.
Are you using a serial console? Or, a defferent question, are
Hi,
I seem to get inconsistent outputs from the same dummynet
stat query. Following is the output from two different queries :
bash-2.05$
bash-2.05$ ipfw pipe 3 show
3: unlimited0 ms 2048 B 0 queues (1 buckets) droptail
mask: 0x00 0x/0x - 0x/0x
bash-2.05$
On Fri, Oct 26, 2001 at 10:22:48AM -0700, rick norman wrote:
Hi,
I seem to get inconsistent outputs from the same dummynet
stat query. Following is the output from two different queries :
bash-2.05$
bash-2.05$ ipfw pipe 3 show
3: unlimited0 ms 2048 B 0 queues (1 buckets)
I guess my question then is why did I need to stop the stream and restart
it before it would show up in the pipe? It seems that if I repeatedly flush,
delete pipes, reinstall pipes, without stopping the data stream, that I get
into
a state where no data will register in the pipes until I stop
I didn't see anything like this in the archives, so I'm sending this to
the questions list and hackers list for assistance.
I am running FreeBSD 4.3 on a L440GX+ motherboard with dual PCI buses: 32/33
and 32/66 dual Pentium III @ 700MHz with 256KB L2 cache.
The system is running in Uniprocessor
If syslogd used the kqueue interface, I believe it could open a new log
file as soon as it was created, rather than waiting to receive a signal.
Would this be worth doing, or would it be too big a divergence from the
traditional behavior?
--
Ben
An art scene of delight
I created this to be
On Fri, Oct 26, 2001 at 09:15:28AM +0200, Peter Wullinger wrote:
Have I just missed, that anoncvs.FreeBSD.org was shut down?
This would be a problem for me since I do not have access to
a FreeBSD machine with good internet connection and I didn't
get cvsup (i.e. M3) to compile on the
On Fri, Oct 26, 2001 at 11:39:57PM +0100, void wrote:
If syslogd used the kqueue interface, I believe it could open a new log
file as soon as it was created, rather than waiting to receive a signal.
Would this be worth doing, or would it be too big a divergence from the
traditional behavior?
void [EMAIL PROTECTED] writes:
On Fri, Oct 26, 2001 at 08:04:36PM -0700, Kris Kennaway wrote:
I assume you mean as soon as the configuration file is modified?
That would be a big violation of POLA.
No ...
Yes!
The traditional log-rotation dance goes something like:
mv log log.0
Mike Barcroft [EMAIL PROTECTED] writes:
void [EMAIL PROTECTED] writes:
On Fri, Oct 26, 2001 at 08:04:36PM -0700, Kris Kennaway wrote:
I assume you mean as soon as the configuration file is modified?
That would be a big violation of POLA.
No ...
Yes!
Just to clarify. This is
On Sat, Oct 27, 2001 at 12:26:22AM -0400 I heard the voice of
Mike Barcroft, and lo! it spake thus:
Just to clarify. This is still a POLA violation. If a log file is
pulled out from underneath syslogd(8), one wouldn't expect it to start
logging again, even if the file was re-created. Just
24 matches
Mail list logo
