-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kris Kennaway wrote:
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Kris Kennaway wrote:
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Here are lock profiling results with
El jueves 10 de enero a las 01:10:17 CET, Julian H. Stacey escribió:
Julian H. Stacey wrote:
I too saw mountd / exports just fail on 2 systems upgraded in last
days from 7RC4 to newest 7 Stable (CTM src-7 80, received here Jan
6 15:15 CEST=GMT+01:00). I am not using .snap snapshot. My
My apologies for posting this both to the Rancid list and FreeBSD-STABLE,
however I am not sure where to start troubleshooting this issue - I am
suspecting it is a FreeBSD issue, but I am thinking we are probably not
the only shop running RANCID (ports/net-mgmt/rancid) on FreeBSD (since it
is
Lars Erik Gullerud wrote:
So it only seems to be on newer FreeBSD with SMP. (If anyone have
RANCID working okay on FreeBSD 6.x/7.x on SMP systems at all, please
let me know...)
This probably won't be of much help, I figured I'd chime in anyway since
it may effect me in the future, but I
Hi Lars,
You should use expect-devel port to avoid hunging on pty
have a look at
http://www.freebsd.org/cgi/query-pr.cgi?pr=118452
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300
On Wednesday 09 January 2008 07:06:02 pm Xin LI wrote:
Richard Bates wrote:
Sorry for the repost...
I don't think the first one posted..
posted to freebsd.stable, freebsd-current, Freebsd-hardware
I checked the hardware in the online documentation manual/hardware
It only lists the
On Thu, 10 Jan 2008 07:33:03 +0200, Kostik Belousov [EMAIL PROTECTED] wrote:
For the SU-imposed jerkiness, try the patch below. Progress on developing
the change stalled somehow, and I would like to process with it.
diff --git a/sys/kern/vfs_mount.c b/sys/kern/vfs_mount.c
index
Kris Kennaway wrote:
OK. Can you obtain a lock profiling dump?
I'm trying, but not succeeding so far. I added the following to the kernel
config:
options MUTEX_PROFILING
options MPROF_BUFFERS=1536
options MPROF_HASH_SIZE=1543
And set debug.mutex.prof.enable=1
Toomas Aas wrote:
Kris Kennaway wrote:
OK. Can you obtain a lock profiling dump?
I'm trying, but not succeeding so far. I added the following to the
kernel config:
options MUTEX_PROFILING
options MPROF_BUFFERS=1536
options MPROF_HASH_SIZE=1543
And set
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kris Kennaway wrote:
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Kris Kennaway wrote:
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Here are lock
Seems our current libarchive? That support FreeBSD's tar implementation has
a bug where it can create archives it cant read back. This can be seen
by simply creating an empty tar.gz file and then trying to expand or
list it.
In doing the above you get the following error:
tar: Unrecognized
On Jan 10, 2008, at 2:58 PM, Steven Hartland wrote:
Seems our current libarchive? That support FreeBSD's tar
implementation has
a bug where it can create archives it cant read back. This can be seen
by simply creating an empty tar.gz file and then trying to expand or
list it.
In doing the
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz
tar: Unrecognized archive format: Inappropriate file type or format
tar --version
bsdtar 1.2.53 - libarchive 1.2.53
gtar tvzf test.tar.gz
gtar --version
tar (GNU
On Thu, Jan 10, 2008 at 11:55:52PM -, Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz
tar: Unrecognized archive format: Inappropriate file type or format
tar --version
bsdtar
Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz tar: Unrecognized archive format: Inappropriate
file type or format
tar --version
bsdtar 1.2.53 - libarchive 1.2.53
gtar tvzf test.tar.gz
On Thu, Jan 10, 2008 at 11:55:52PM -, Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz tar: Unrecognized archive format: Inappropriate file
type or format
tar --version
bsdtar
- Original Message -
From: Kris Kennaway [EMAIL PROTECTED]
Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz tar: Unrecognized archive format: Inappropriate
file type or format
Steven Hartland wrote:
- Original Message - From: Kris Kennaway [EMAIL PROTECTED]
Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz tar: Unrecognized archive format: Inappropriate
On Jan 10, 2008, at 4:41 PM, Kris Kennaway wrote:
Not that I'm aware of. gtar works but libarchive tar fails on
the file it created.
Yes, in 6.2. What about the report that it works in 6.3?
Indeed. Trying to create a tarball using a non-existent list of files
returns an error and
On 11/01/2008, at 11:47 AM, Chuck Swiger wrote:
On Jan 10, 2008, at 4:41 PM, Kris Kennaway wrote:
Not that I'm aware of. gtar works but libarchive tar fails on
the file it created.
Yes, in 6.2. What about the report that it works in 6.3?
Indeed. Trying to create a tarball using a
From: Mikhail Teterin [EMAIL PROTECTED]
Date: Thu, 27 Dec 2007 12:39:21 -0500
Sender: [EMAIL PROTECTED]
ÞÅÔ×ÅÒ 27 ÇÒÕÄÅÎØ 2007 12:33 ÐÏ, M. Warner Losh ÷É ÎÁÐÉÓÁÌÉ:
I did the bulk of the work for the 7.0 stuff, at least getting things
into the tree. Since I did the work, my last job got
Richard,
I just bought one of these 2450 servers on ebay the other day, it was
pretty cheap and still a good server for DNS
here is a link
http://search.ebay.com/_W0QQsassZlesmilde
when I received the server it shipped with PC-BSD installed, I am
going to put RELENG_7 on it, but if you read the
On Fri, 11 Jan 2008 01:08:59 +0100
Kris Kennaway [EMAIL PROTECTED] wrote:
Steven Hartland wrote:
A totally empty file is not valid try the following test:-
touch empty
tar cvzf test.tar.gz --files-from empty
tar tvzf test.tar.gz tar: Unrecognized archive format: Inappropriate
file
23 matches
Mail list logo
