Marc G. Fournier [EMAIL PROTECTED] writes:
You've all lost me here ... what exactly is the problem?
You can't run multiple instances of PostgreSQL on the same machine
(even in chroot or jail, even without TCP/IP support) without changing
the port number in postgresql.conf. PostgreSQL creates
Hi All,
Just had a strange problem with my desktop.
I rebuilt world from sources downloaded a few hours ago, rebooted and
everything worked fine. Then I noticed that I had HTT turned off,
rebooted, enabled HTT in the bios and booted up again. The system
seemed to work ok, until I tried loading
Hi!
I've been using gmirror for a while to safeguard my system disks. I have
taken the slice-based mirror approach, where I use, say, ad0s1 and ad2s1 as
providers.
On one of my servers, this seems to be impossible. I create the mirror using
ad2s1 first (to keep my system running while I do some
Oliver Fromme wrote:
Uwe Doering [EMAIL PROTECTED] wrote:
Oliver Fromme wrote:
If they're really identical (i.e. the same size and same
geometry), then you can use dd(1) for duplication, like
this:
# dd if=/dev/ad0 of=/dev/ad1 bs=64k conv=noerror,sync
The noerror,sync part
In message [EMAIL PROTECTED], Danny Braniss writes:
after doing a mount_nfs as root (from the console or via su), statfs reports
that MNT_USER flags is set! this is also true with 5.4.
It's a bug in the statfs reporting for NFS filesystems. It should
be fixed now in -CURRENT (revision
Danny Braniss wrote:
BTW, this, the MNT_NOEXEC, uncovered, IMHO, a bug in libexec/rtld-elf/rtld.c
where it's now checking for MNT_NOEXEC, but only if LD_LIBRARY_PATH is set!
This is not a bug. Checking for MNT_NOEXEC adds a cost in performance, and
it is not necessary if LD_LIBRARY_PATH,
Hi,
Panic on RELENG_5_4 (cvsup yesterday).
Waiting 5 seconds for SCSI devices to settle
panic: mutex Giant not owned at /usr/src/cam/cam_xpt.c:4825
cpuid = 0
KDB: enter: panic
[thread pid 35 tid 100031 ]
Stopped at kdb_enter+0x2b: nop
db where
Tracing pid 35 tid 100031 td 0xc22fb180
On Tue, May 03, 2005 at 11:47:00AM +0200, Marc Olzheim wrote:
On Wed, Apr 27, 2005 at 12:08:57PM -0400, Brian Fundakowski Feldman wrote:
Alright, this will do synchronous, instead of short, writes (also,
of course, not deadlock the system) if you are trying to use an
excessively large
FreeBSD 5.4-STABLE #12: Mon May 2 19:23:22 CEST 2005 [EMAIL
PROTECTED]:/usr/obj/usr/src/sys/HAMMER
hammer:~/src/hak/fpugdb ./fpu5th
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to
On Tue, May 03, 2005 at 04:43:13PM +0200, Marc Olzheim wrote:
FreeBSD 5.4-STABLE #12: Mon May 2 19:23:22 CEST 2005 [EMAIL
PROTECTED]:/usr/obj/usr/src/sys/HAMMER
Doing exactly the same on i386 SMP results in a hanging gdb and the
process exiting with signal 8.
blackmetal:~#ps uaxwlp 759
Is this going to be fixed before 5.4 ? It still breaks on today's
5.4-STABLE.
Marc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Tue, 3 May 2005, [iso-8859-1] Dag-Erling Smørgrav wrote:
PostgreSQL has always had this problem, both on 4.x and 5.x. A hack was
put in place last November to work around it, but it still exists, and
while it may now be possible (with 8.0) for multiple postmasters to run
on the same machine
I just tried RELENG_5 as of last week and the latest (April 13) ATA
mkIII patches from http://people.freebsd.org/~sos/ATA/ on my laptop.
Unfortunately, it breaks suspend-to-RAM (S3).
History:
I first tried RELENG_5 on the laptop (a Toshiba Tecra M2V) in January
and suspend did not work (the
Just been trying to install a new machine with 5.4-RC4. I normally
do this using the bootonly image and FTP. But doing an FTP install
always gives me the error /: write failed, filesystem full when
it fetches the first chunk and tries to write it out.
I get exactly the same problem doing an FTP
Andrew Heybey wrote:
I just tried RELENG_5 as of last week and the latest (April 13) ATA
mkIII patches from http://people.freebsd.org/~sos/ATA/ on my laptop.
Unfortunately, it breaks suspend-to-RAM (S3).
History:
I first tried RELENG_5 on the laptop (a Toshiba Tecra M2V) in January
and suspend
Marcus Grando wrote:
Hi,
Panic on RELENG_5_4 (cvsup yesterday).
Waiting 5 seconds for SCSI devices to settle
panic: mutex Giant not owned at /usr/src/cam/cam_xpt.c:4825
cpuid = 0
KDB: enter: panic
[thread pid 35 tid 100031 ]
Stopped at kdb_enter+0x2b: nop
db where
Tracing pid 35 tid 100031 td
On Mon, 2 May 2005, Jonathan Noack wrote:
Hi I am abit confused here, have seen a post from someone using
5.4-STABLE how is that possible if 5.4 isnt RELEASE yet, and good news
on the bug fix.
When RELENG_5_4 was branched, RELENG_5 went from 5.4-PRERELEASE to
5.4-STABLE to reflect that it is once
Marcus Grando wrote:
Hi,
Panic on RELENG_5_4 (cvsup yesterday).
Waiting 5 seconds for SCSI devices to settle
panic: mutex Giant not owned at /usr/src/cam/cam_xpt.c:4825
cpuid = 0
KDB: enter: panic
[thread pid 35 tid 100031 ]
Stopped at kdb_enter+0x2b: nop
db where
Tracing pid 35 tid 100031 td
On Tue, 2005-05-03 at 16:54 +0100, Pete French wrote:
Just been trying to install a new machine with 5.4-RC4. I normally
do this using the bootonly image and FTP. But doing an FTP install
always gives me the error /: write failed, filesystem full when
it fetches the first chunk and tries to
Eirik Øverby writes:
Hi!
I've been using gmirror for a while to safeguard my system disks. I have
taken the slice-based mirror approach, where I use, say, ad0s1 and ad2s1 as
providers.
On one of my servers, this seems to be impossible. I create the mirror using
ad2s1 first (to keep
. However I can't reproduce the panic in question, so if you're
good at triggering the panic give this a spin.
http://people.freebsd.org/~dwhite/tty.c.20050503.patch
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
On 03-05-05 20:34, George Hartzell [EMAIL PROTECTED] wrote:
Eirik Øverby writes:
Hi!
I've been using gmirror for a while to safeguard my system disks. I have
taken the slice-based mirror approach, where I use, say, ad0s1 and ad2s1 as
providers.
On one of my servers, this seems to be
On Tue, May 03, 2005 at 11:34:06AM -0700, George Hartzell wrote:
The fix is described in the fourth comment block of Ralf's doc, either
make the slice a sector smaller than the disk device or hardcode the
provider name. I've been using the hardcoding approach, and it seems
to work for me.
On Tue, May 03, 2005 at 02:38:08PM -0500, Craig Boston wrote:
I'm sorry that I don't remember who said it (I'll do some googling and
follow up if I can find the reference), but one time this came up
someone posted a very good idea which IMHO is a good enough solution to
make the default. That
Marc G. Fournier [EMAIL PROTECTED] writes:
'k, I've been doing multiple since 7.2 on the same machine, all on the
same port, all different IPs, all on 4.x servers ... have never had an
issue with crashes (its pretty much my most stable 4.x server) ...
It was never possible. 8.0 has a hack to
Darren Pilgrim wrote:
From: Darren Pilgrim
From: Carl Gustavsson [EMAIL PROTECTED]
Have you tested the iwi-driver?
See: http://damien.bergamini.free.fr/ipw/iwi-freebsd.html
I haven't yet. Reading that page has brought up another questions. On
the
page it says 5-STABLE
26 matches
Mail list logo