Hi
Mark Linimon wrote:
I used 7.0-BETA3 and it is much worse.
Ouch. A lot of systems see improvement. Thanks for trying it
out. I hope that one of the people that has been doing the actual
work can now comment (I am just an onlooker), and that you can be
patient in the meantime.
Hi
Alexey Popov wrote:
Now we also have terribly performing PostgreSQL on 8-core server. We
noticed the slowdown after moving PostgreSQL from 2xXeon 3.0
Apache+PostgreSQL server to dedicated PostgreSQL server. I collected
some stats (see attach) before moving to Linux.
Sorry for the broken
On 3/12/2007 8:50 PM, Alexey Popov wrote:
Hi
Alexey Popov wrote:
Now we also have terribly performing PostgreSQL on 8-core server. We
noticed the slowdown after moving PostgreSQL from 2xXeon 3.0
Apache+PostgreSQL server to dedicated PostgreSQL server. I collected
some stats (see attach)
Hi,
Antony Mawer wrote:
On 3/12/2007 1:37 PM, Tim Daneliuk wrote:
Jack Vogel wrote:
On Dec 1, 2007 8:32 PM, Daniel O'Connor [EMAIL PROTECTED] wrote:
Hi,
I am doing some work for a company that recently bought 2 systems
based
on the above motherboard and mostly they work fine, however on
On Mon, 3 Dec 2007, Alexey Popov wrote:
Mark Linimon wrote:
I used 7.0-BETA3 and it is much worse.
Ouch. A lot of systems see improvement. Thanks for trying it out. I hope
that one of the people that has been doing the actual work can now comment
(I am just an onlooker), and that you can
Hi,
On Sun, Dec 02, 2007 at 09:49:38PM +0100, Gelsema, P (Patrick) wrote:
batman# zfs create public/jail/public
internal error: failed to initialize ZFS library
In /var/log/messages on the host I get the following:
Dec 2 21:47:01 hulk kernel: WARNING pid 36752 (zfs): ioctl sign-extension
Hi
Alexey Popov wrote:
Now we also have terribly performing PostgreSQL on 8-core server. We
noticed the slowdown after moving PostgreSQL from 2xXeon 3.0
Apache+PostgreSQL server to dedicated PostgreSQL server. I collected
some stats (see attach) before moving to Linux.
FYI there's top output
On Mon, December 3, 2007 12:54, Oliver Brandmueller wrote:
Hi,
On Sun, Dec 02, 2007 at 09:49:38PM +0100, Gelsema, P (Patrick) wrote:
batman# zfs create public/jail/public
internal error: failed to initialize ZFS library
In /var/log/messages on the host I get the following:
Dec 2 21:47:01
Antony Mawer wrote:
Have you tried testing with different values for kern.hz? I am by no
means an expert, but have stumbled across various postings over the past
few years that suggest the high value (1000) used by modern (5.x+?)
kernels can be pessimistic for some workloads...
If you
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot file
from TFTP server,
then trying to load kernel image from TFTP server.
After 10-20 minutes it give me error message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Repost from [EMAIL PROTECTED]
As has been hashed out in -ports@ over the last few days there is at
least a need to examine weither or not the current ports system should
remain as is or potentially be re-engineered in the future (estimates
if and
try monitoring the traffic (tcpdump/wireshark), this should give you
a good starting point.
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Dewayne Geraghty wrote:
We're looking to deploy FreeBSD on our main firewall. The firewall config
is a VIA C7 (padlock), racoon(ipsec-tools-0.7), IPSec. We're testing racoon
with a windows box, however the firewall doesn't function correctly when
net.inet.ipsec.crypto_support=1 is set. With
On Mon, December 3, 2007 14:20, Andrew Kolchoogin wrote:
On Mon, December 3, 2007 14:02, Andrew Kolchoogin wrote:
Did you add the zfs device to be available for your jails in
devfs.rules? In the ruleset applying for the jails you need to add:
add path zfs unhide
hulk is the host,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
7. Same as question 6 but for your answer on question 3?
This should read:
7. If the new system corrected the worst aspect of the current system
but broke the best aspect of it would you use the new system?
- --
Aryeh M. Friedman
FloSoft Systems
Hi.
Robert Watson wrote:
Is there any other FreeBSD developer who can take care of performance
problems on many-cores systems? Seems like upcoming 7-RELEASE and
6.3-RELEASE would be completely unusable for us on that kind of
systems i.e. mostly on all modern hardware.
There are many FreeBSD
On Mon, Dec 03, 2007 at 09:31:55PM +0800, Balgansuren Batsukh wrote:
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot file
from TFTP server,
then trying to load kernel
On Mon, 3 Dec 2007 21:31:55 +0800 Balgansuren Batsukh wrote:
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully
finish my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot
file from TFTP server,
then trying to load kernel image from TFTP
hi!.. i'm not able to change file permission to disable rlogin and
login on my box even as root
# ls -lo /usr/bin/login /usr/bin/rlogin
-r-sr-xr-x 1 root wheel schg 19996 Dec 1 13:04 /usr/bin/login
-r-sr-xr-x 1 root wheel schg 10140 Dec 1 13:04 /usr/bin/rlogin
# chflags -R nouchg login
Aryeh M. Friedman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Repost from [EMAIL PROTECTED]
As has been hashed out in -ports@ over the last few days there is at
least a need to examine weither or not the current ports system should
remain as is or potentially be re-engineered in the
On Mon, 3 Dec 2007 07:41:49 -0800 Jeremy Chadwick wrote:
I've tried this before myself (on all sorts of different hardware), and
I've never gotten it to work on RELENG_6 or RELENG_7 -- I reach the same
point and receive the same error you do.
We use diskless setup in production. It works just
Anjang Aki wrote:
hi!.. i'm not able to change file permission to disable rlogin and
login on my box even as root
# ls -lo /usr/bin/login /usr/bin/rlogin
-r-sr-xr-x 1 root wheel schg 19996 Dec 1 13:04 /usr/bin/login
-r-sr-xr-x 1 root wheel schg 10140 Dec 1 13:04 /usr/bin/rlogin
#
On Dec 3, 2007 4:59 PM, Anjang Aki [EMAIL PROTECTED] wrote:
# chflags -R nouchg login rlogin
chflags: /usr/bin/login: Operation not permitted
chflags: /usr/bin/rlogin: Operation not permitted
# chmod a=rx /usr/bin/login /usr/bin/rlogin
chmod: /usr/bin/login: Operation not permitted
chmod:
On Mon, 3 Dec 2007, Alexey Popov wrote:
Robert Watson wrote:
Is there any other FreeBSD developer who can take care of performance
problems on many-cores systems? Seems like upcoming 7-RELEASE and
6.3-RELEASE would be completely unusable for us on that kind of systems
i.e. mostly on all
i just got the answer..
i need to run init 1 and do chflags -R 0 /usr/bin/rlogin and then i
can change the file permission using chmod
thanks for your advice
On 12/4/07, Michael Proto [EMAIL PROTECTED] wrote:
Anjang Aki wrote:
hi!.. i'm not able to change file permission to disable rlogin and
On Dec 3, 2007, at 9:39 AM, Michael Proto wrote:
Not that this solves your problem, but doesn't the padlock crypto
engine
only provide acceleration for AES symmetric encryption? From the man
page:
The boot messages on my C7 based system shows this:
PadLock: HW support loaded for
On Mon, 19 Nov 2007 16:29:38 -0500, J.R. Oldroyd [EMAIL PROTECTED] wrote:
[7.0b3 on a Sony VAIO laptop with an ALPS GlidePoint touchpad.
System ran 6.2 and earlier FreeBSD versions without problems.]
3. occasionally when moving the cursor using the touchpad, the coordinates
suddenly
Hello Pyun,
This is a new server with latest RELENG_7 src and latest BIOS as well.
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
The Regents of the University of California. All rights
reserved.
FreeBSD is a
My apologies for the confusion, yes, the C7 only helps with AES.
The configuration detail is: between branch offices I use FreeBSD ipsec
(AES), and within the branches Windows boxes access the firewall boxes. The
firewalls run samba inside a jail. Due to sensitive information (see your
local
On Mon, 3 Dec 2007, Anjang Aki wrote:
hi!.. i'm not able to change file permission to disable rlogin and login on
my box even as root
# ls -lo /usr/bin/login /usr/bin/rlogin
-r-sr-xr-x 1 root wheel schg 19996 Dec 1 13:04 /usr/bin/login
-r-sr-xr-x 1 root wheel schg 10140 Dec 1 13:04
Dewayne Geraghty wrote:
My apologies for the confusion, yes, the C7 only helps with AES.
The configuration detail is: between branch offices I use FreeBSD ipsec
(AES), and within the branches Windows boxes access the firewall boxes. The
firewalls run samba inside a jail. Due to sensitive
On Mon, Dec 03, 2007 at 09:19:15AM -0500, Aryeh M. Friedman wrote:
1. What is more important to your personal use of FreeBSD (the ports
system, the underlaying OS, some other aspect)?
Yes. (i.e., mu)
2. How frequently do you interact with the ports systems and what is
the most common
(If you aren't interested in the details of our ptmx/pty/pts driver, skip to
the paragraph that reads So, why the long-winded story?)
Dear all:
The current ptmx/pts implementation makes use of devfs(4) cloning: a user
process wanting to allocate a pty/pts pair opens /dev/ptmx, which returns
TB --- 2007-12-04 00:31:07 - tinderbox 2.3 running on freebsd-legacy.sentex.ca
TB --- 2007-12-04 00:31:07 - starting RELENG_6 tinderbox run for i386/i386
TB --- 2007-12-04 00:31:07 - cleaning the object tree
TB --- 2007-12-04 00:31:51 - cvsupping the source tree
TB --- 2007-12-04 00:31:51 -
TB --- 2007-12-04 00:30:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca
TB --- 2007-12-04 00:30:30 - starting RELENG_6 tinderbox run for amd64/amd64
TB --- 2007-12-04 00:30:30 - cleaning the object tree
TB --- 2007-12-04 00:31:15 - cvsupping the source tree
TB --- 2007-12-04 00:31:15 -
On Mon, Dec 03, 2007 at 12:52:33PM -0800, Abdullah Ibn Hamad Al-Marri wrote:
Hello Pyun,
This is a new server with latest RELENG_7 src and latest BIOS as well.
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
On Mon, 3 Dec 2007, Antony Mawer wrote:
Another me too. We saw this and wound up removing the floppy drive
from the systems in order to avoid this lengthy delay on boot - we
weren't using them anyway and it saved a whole $5 or so on the
hardware costs... ;-)
I seem to recall it was not
Aryeh M. Friedman wrote:
1. What is more important to your personal use of FreeBSD (the ports
system, the underlaying OS, some other aspect)?
2. How frequently do you interact with the ports systems and what is
the most common interaction you have with it?
Portupgrade a few times a
TB --- 2007-12-04 00:32:27 - tinderbox 2.3 running on freebsd-legacy.sentex.ca
TB --- 2007-12-04 00:32:27 - starting RELENG_6 tinderbox run for i386/pc98
TB --- 2007-12-04 00:32:27 - cleaning the object tree
TB --- 2007-12-04 00:33:10 - cvsupping the source tree
TB --- 2007-12-04 00:33:10 -
Aryeh M. Friedman wrote:
[Repost from [EMAIL PROTECTED]
As has been hashed out in -ports@ over the last few days there is at
least a need to examine weither or not the current ports system should
remain as is or potentially be re-engineered in the future (estimates
if and when needed vary
At 09:28 PM 12/3/2007, Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this related to the commit that just went through to enable on arch that
support it?
One way to check is to take a look at the status page for the tinderboxes
http://tinderbox.des.no/
which are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this related to the commit that just went through to enable on arch that
support it?
=== gnu/usr.bin/gdb/gdbserver (clean)
cd: can't cd to /usr/src/gnu/usr.bin/gdb/gdbserver
*** Error code 2
Stop in /usr/src/gnu/usr.bin/gdb.
Or did I catch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great, thank you ... bookmarked ... so, should one not report something like
this if that page shows it as a failure?
- --On Monday, December 03, 2007 21:57:50 -0500 Mike Tancsa [EMAIL PROTECTED]
wrote:
At 09:28 PM 12/3/2007, Marc G. Fournier
At 10:27 PM 12/3/2007, Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great, thank you ... bookmarked ... so, should one not report something like
this if that page shows it as a failure?
Its automatically reported to the mailing list. eg.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teach me to sort threaded :(
Thanks ...
- --On Monday, December 03, 2007 22:34:55 -0500 Mike Tancsa [EMAIL PROTECTED]
wrote:
At 10:27 PM 12/3/2007, Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Great, thank you ...
On Mon, 2007-12-03 at 21:31 +0800, Balgansuren Batsukh wrote:
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot file
from TFTP server,
then trying to load kernel
46 matches
Mail list logo
