On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote:
tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1
34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514
127.0.0.1.643: . ack 30 win 65535
0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 F..,[EMAIL
PROTECTED]
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote:
most files in /etc/rc.d changed, so installing them all with
mergemaster was laborious - a note in UPDATING similar to that for
5.x:
The simplest solution is an 'rm -rf /etc/rc.d/*' and then
On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote:
Hi,
I'm running FreeBSD 5-Stable.
I only seem to encounter this problem with the
math/graphical port 'grace', and the dlopen()
call inthere.
I answered this question the last time you posted it.
Kris
pgpQ418EGqdDv.pgp
Description:
Confirmed, no more leaks. I put it 1 hour ago onto 1 production server,
and today evening I'll put it to another one. Every server serves up to 2
million SMTP connections per day: load are heavy. Both servers SMP.
Gleb Smirnoff wrote:
GS please confirm that the attached patch fix your problem.
dawnshade wrote:
On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote:
tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1
34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514
127.0.0.1.643: . ack 30 win 65535
0x: 4600 002c 6605 4000 0306 11c5 7f00 0001 F..,[EMAIL PROTECTED]
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote:
I'm running FreeBSD 5-Stable.
I only seem to encounter this problem with the
math/graphical port 'grace', and the dlopen()
call inthere.
I answered this question the last time you
On Wed, Oct 26, 2005 at 01:16:46AM -0700, Rob wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote:
I'm running FreeBSD 5-Stable.
I only seem to encounter this problem with the
math/graphical port 'grace', and the dlopen()
dawnshade wrote:
On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote:
On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote:
tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1
34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514
127.0.0.1.643: . ack 30 win 65535
0x:
On Wednesday 26 October 2005 12:41, Anton Nikiforov wrote:
dawnshade wrote:
On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote:
On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote:
tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1
34 rule 0/3(short): pass out on lo0: IP
Alexander 'alxl' Lobachov wrote:
Hello,
Just cvsuped and built the kernel and installed it ok, buildworld went
clear also, tried to installworld and got this:
$ sudo make installworld
mkdir -p /tmp/install.QhTsbtJk
for prog in [ awk cap_mkdb cat chflags chmod chown date
echo egrep find grep
dawnshade wrote:
maybe this link help you.:
http://groups.google.com/group/fido7.ru.unix.bsd/msg/187bf3d7de6e3eab?dmode=source
Sorry to other subscribers - it in russian.
short fix problem: replace 'pass quick all lo0' to 'pass qucik all allow-opts
lo0'
On 10/25/05, Dan Charrois [EMAIL PROTECTED] wrote:
Hi all. I'm wondering if anyone can shed some light on a strange
crashing/rebooting problem I'm having. First, the specs:
Hardware: Dell PowerEdge 2850 rack mounted server, Dual 3.4 Ghz Xeon,
5 Gb memory
[snip]
You didn't mention, have
On Wednesday 26 October 2005 12:08, Anton Nikiforov wrote:
On Tuesday 25 October 2005 23:21, Anton Nikiforov wrote:
tcpdump -n -e -ttt -x -i pflog0 host 127.0.0.1
34 rule 0/3(short): pass out on lo0: IP 127.0.0.1.514
127.0.0.1.643: . ack 30 win 65535
0x: 4600 002c 6605
I am the only FreeBSD user on the Grace mailinglist.
Apparently the dlopen() call in grace works fine
on Linux and others. But not with FreeBSD.
This is not a problem with the dlopen call *or* freebsd - the
problem is that it is asking for a library 'libXcursor.so.1.0'
which does not exist on
On Tue, 2005-Oct-25 20:41:33 -0700, Rob wrote:
2. Create $HOME/.grace/gracerc.user and put
one line in this file:
USE pow TYPE f_of_dd FROM /usr/lib/libm.so
(this is the example from the Grace UsersGuide)
Does grace work correctly if you don't include this line?
3. Start grace like
--- Pete French [EMAIL PROTECTED] wrote:
I am the only FreeBSD user on the Grace
mailinglist.
Apparently the dlopen() call in grace works fine
on Linux and others. But not with FreeBSD.
This is not a problem with the dlopen call *or*
freebsd - the problem is that it is asking for
a
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Oct-25 20:41:33 -0700, Rob wrote:
2. Create $HOME/.grace/gracerc.user and put
one line in this file:
USE pow TYPE f_of_dd FROM /usr/lib/libm.so
(this is the example from the Grace UsersGuide)
Does grace work correctly if
Chris wrote:
Ok thanks I already use it for ports, but just plain -O2 -pipe for the
world and kernel.
Hmm ... I find this thread surprising, as this is the first I have heard
of FreeBSD working correctly with -O2. So, is this the options
suggested for make.conf on x86?
CFLAGS= -O2
I don't know whether this is worth filing a PR for, but it seems the
resolver no longer likes leading zeroes in an IP4 address in /etc/hosts.
The change (in 5- ) appeared sometime in the last month or two.
Personally I'm inclined to view this as a regression although it's
simple enough to work
I don't know whether this is worth filing a PR for, but it seems the
resolver no longer likes leading zeroes in an IP4 address in /etc/hosts.
The change (in 5- ) appeared sometime in the last month or two.
Personally I'm inclined to view this as a regression although it's
simple enough
On Mer 26 octobre 2005 15:43, Thomas T. Veldhouse wrote:
Chris wrote:
Ok thanks I already use it for ports, but just plain -O2 -pipe for the
world and kernel.
Hmm ... I find this thread surprising, as this is the first I have heard
of FreeBSD working correctly with -O2. So, is this the
First, the 'traceall' command has been renamed to 'alltrace'. This allows
abbreviated versions of 'trace' such as 't' or 'tr' to work again. It is
also more consistent with other ddb functions that dump data about multiple
objects ('show allpcpu', etc.).
Secondly, 'bt' has been added as a
Taken from the digest form, so hopefully I won't whack the formatting
too badly.
Dan Charrois [EMAIL PROTECTED] wrote:
[snip]
No, I haven't been able to run diagnostics and rule out the hardware
for two reasons.. First, the server is located about an hour's drive
away, and I haven't
I've been seeing a number of strange messages in my log since
updating to 6.0-RC1. Usually they happen when some intense
disk access is happening (e.g. when /etc/periodic/security/100.chksetuid
is running at 03:01), but it doesn't happen _every_ morning, and
it doesn't always happen if I manually
On Wed, Oct 26, 2005 at 01:05:04AM -0400, Bryan Fullerton wrote:
...
You didn't mention, have you run Dell diagnostics on the machine to
rule out hardware issues?
While those diagnostics may well demostrate that a problem exists, the
lack of a problme is not demonstrated by a machine passing
On Wed, Oct 26, 2005 at 10:46:43AM +1000, Joel Hatton wrote:
/etc/usbd.conf has lost the [Device] configuration for the mouse,
which although doesn't prevent the mouse from working, it did mean
that I had to add those lines again so that I could turn on '-z
4' for the
On 2005-10-26, Mark Andrews wrote:
Leading zeros are ambigious. Some platforms treat them as octal
others treat them as decimal.
There is nothing ambiguous about the example provided. (Perhaps
it wasn't a good example, but it's always a bug if '04' is not
correctly decoded,
wicontrol.c defaults to the wi interface. I used to have a
wi device, but it eventually took a dump and I bought a new
ath-based card, which works flawlessly AFAIK, after four months
or so.
But I grow weary of having to specify -i ath0 every time I
run wicontrol.
Please review the following
On Wed, Oct 26, 2005 at 03:20:47PM -0700, James Long wrote:
wicontrol.c defaults to the wi interface. I used to have a
wi device, but it eventually took a dump and I bought a new
ath-based card, which works flawlessly AFAIK, after four months
or so.
But I grow weary of having to specify -i
On 2005-10-26, Mark Andrews wrote:
Leading zeros are ambigious. Some platforms treat them as octal
others treat them as decimal.
There is nothing ambiguous about the example provided. (Perhaps
it wasn't a good example, but it's always a bug if '04' is not
correctly decoded, regardless
wicontrol is obsolete and you should not need to use it, particularly
for ath(4) devices. Why are you using it? Is some feature you need
missing from ifconfig?
The command I use most is wicontrol -L
___
freebsd-stable@freebsd.org mailing list
On 2005-10-26, Matt Emmerton wrote:
On 2005-10-26, Mark Andrews wrote:
Leading zeros are ambigious. Some platforms treat them as octal
others treat them as decimal.
There is nothing ambiguous about the example provided. (Perhaps
it wasn't a good example, but it's always a bug if
On 2005-10-26, Mark Andrews wrote:
Leading zeros are ambigious. Some platforms treat them as octal
others treat them as decimal.
There is nothing ambiguous about the example provided. (Perhaps
it wasn't a good example, but it's always a bug if '04' is not
correctly decoded,
On Thu, 27 Oct 2005 09:31, James Long wrote:
wicontrol is obsolete and you should not need to use it, particularly
for ath(4) devices. Why are you using it? Is some feature you need
missing from ifconfig?
The command I use most is wicontrol -L
Try ifconfig ath0 list scan
--
Daniel
Le Mercredi 26 Octobre 2005 02:46, Joel Hatton a écrit :
most files in /etc/rc.d changed, so installing them all with
mergemaster was laborious - a note in UPDATING similar to that for
5.x:
The simplest solution is an 'rm -rf /etc/rc.d/*' and then
35 matches
Mail list logo
