Στις Tuesday 15 July 2008 19:58:12 ο/η Achilleas Mantzios έγραψε:
Hi,
The problem started when i installed a kodicom 4400 card and started to run
zoneminder.
Prior to that no problems with my machine, which now runs
FreeBSD panix.internal.net 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #3: Mon
Could be memory, but I'd also suggest looking at
temperatures. I've had overheating systems produce lots of
such errors.
Temperature is fine - it never get's that hot here in the UK ;-) Seriously, I
put my hand in the box, touched a few heat sync's, it
is not running hot enough to cause a
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of Kevin K
Sent: Tuesday, July 15, 2008 11:41 PM
To: 'FreeBSD Stable'
Subject: HP Pavilion dv2000 laptop wont boot off install cd
Laptop details :
HP Pavilion dv2000 (dv2422ca)
Specifications (taken from
On Wed, Jul 16, 2008 at 05:03:49AM -0400, Kevin K wrote:
It should be noted that I just tried 6.3-release-amd64 and it doesn't work
as well.
It should also be important to note that sometimes it 'dumps' before getting
to the boot options screen in the freebsd startup.
If I do get to
On 15/07/2008, at 3:54 PM, Jeremy Chadwick wrote:
We moved all of our production systems off of using dump/restore
solely
because of these aspects. We didn't move to ZFS though; we went with
rsync, which is great, except for the fact that it modifies file
atimes
(hope you use Maildir and
We have deployed an IMAP server running on Cyrus on FreeBSD 6.2, with a
500GB UFS2 partition mirrored with geom_mirror and geom_gate across a
dedicated 1gbps link.
It has proven to be very stable and reliable after appropriate tweaking.
The uptime of the mirror is usually 1-3 months,
Kevin K [EMAIL PROTECTED] wrote:
I tried to boot from 7.0-release-AMD64, 7.0-release-i386 and
6.2-release-i386 install disks (about to try 6.3-release-amd64). I could not
successfully boot up the computer using the install disks mentioned.
Sometimes there would be a memory dump (scrolling
Please try one of the more recent 7-stable snapshots
from June or July. They're located on the FTP sites
in /pub/FreeBSD/snapshots.
Best regards
Oliver
This was actually just recommended to me by Gavin Atkinson earlier today. I
am downloading 7.0-STABLE-200806-amd64-disc1.iso right now
Please try one of the more recent 7-stable snapshots
from June or July. They're located on the FTP sites
in /pub/FreeBSD/snapshots.
Best regards
Oliver
This was actually just recommended to me by Gavin Atkinson earlier
today. I
am downloading
John, a question, how is swap set up on your system? I was
swapping to a file (a memory disk device /dev/md0). I was
doing this because for some reason lost in ancient history,
this machine was not set up with a real swap partition.
Hence, no crash dump.
Swap is a partition on the
John Sullivan wrote:
John, a question, how is swap set up on your system? I was
swapping to a file (a memory disk device /dev/md0). I was
doing this because for some reason lost in ancient history,
this machine was not set up with a real swap partition.
Hence, no crash dump.
Swap is a
On Wed, Jul 16, 2008 at 10:38 AM, John Sullivan [EMAIL PROTECTED] wrote:
Could be memory, but I'd also suggest looking at
temperatures. I've had overheating systems produce lots of
such errors.
Temperature is fine - it never get's that hot here in the UK ;-) Seriously,
I put my hand in
Michael Grant wrote:
On Wed, Jul 16, 2008 at 10:38 AM, John Sullivan [EMAIL PROTECTED] wrote:
Could be memory, but I'd also suggest looking at
temperatures. I've had overheating systems produce lots of
such errors.
Temperature is fine - it never get's that hot here in the UK ;-) Seriously, I
At Tue, 15 Jul 2008 10:35:57 -0700,
Jack Vogel wrote:
OK, will put on my todo list :)
Thanks. A kernel built that way (i.e. with igb and em) does actually
work, which is good, but if you're going to split them up we should
get this right before 7.1.
Best,
George
Hello,
I've managed to get sysinstall to do a completely unattended
install via DHCP/PXE and reboot the system into a state
where it will be possible to login via SSH.
So far, so good. Unfortunately This works for VGA consoles only.
If the server in question has got a serial console, I get
this
On Tue, Jul 15, 2008 at 2:57 PM, Paul Horechuk [EMAIL PROTECTED] wrote:
Since upgrading to 7.0 Stable, I've noticed an occasional problem with
konqueror. I've been recompiling my ports for the past few weeks and have
noticed that some sites are complaining about cookies not being enabled.
Hi!
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
binding named to particular IP address when host has many of them?
Using query-source address without port is the
From: John Sullivan [EMAIL PROTECTED]
Date: Wed, 16 Jul 2008 09:38:26 +0100
Could be memory, but I'd also suggest looking at
temperatures. I've had overheating systems produce lots of
such errors.
Temperature is fine - it never get's that hot here in the UK ;-)
Seriously, I put
Eugene Grosbein wrote:
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
binding named to particular IP address when host has many of them?
Using query-source
OK, the first thing to do is disable bg fsck, then force a full fsck of
all filesystems. bg fsck does a poor job of fixing arbitrary
filesystem corruption (it's not designed to do so, in fact), and you
can get into a situation where corrupted filesystems cause further
panics.
Done,
On Thu, 2008-07-03 at 17:14 -0400, Ken Smith wrote:
If any of you have been wishing there was an IPv6-capable cvsup server
you could use (with csup as the client obviously since cvsup doesn't do
IPv6...) give cvsup18.freebsd.org a try. With the help of a few other
folks I got nudged into
On Thu, Jul 17, 2008 at 12:20:42AM +0800, Eugene Grosbein wrote:
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
binding named to particular IP address when host
On Jul 11, 2008, at 4:48 AM, Ronald Klop wrote:
You can try going into the kernel debugger to see where it is
hanging. Debugging via a serial cable is also very easy.
I don't know the details, but there is a lot of info in the Freebsd
handbook. Put this in google 'freebsd handbook kernel
On Jul 11, 2008, at 8:58 AM, Roland Smith wrote:
After about 2 weeks of watching it carefully I've learned almost
nothing. It's not a disk failure (AFAIK) it's not cpu overheat (now
running healthd without complaints) it's not based on any given
network traffic... however it does appear to
On Fri, Jul 11, 2008 at 12:59:33AM -0700, Jo Rhett wrote:
Every time it is rebuilding ad0. Every single boot in the last two
weeks.
On Jul 11, 2008, at 9:49 AM, Clifton Royston wrote:
That just means that it halted without a proper shutdown. If it
crashes, the mirror isn't stopped
On Wed, 16 Jul 2008, Jeremy Chadwick wrote:
On Thu, Jul 17, 2008 at 12:20:42AM +0800, Eugene Grosbein wrote:
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
On Wed, Jul 16, 2008 at 02:23:28PM -0700, Doug Barton wrote:
Jeremy Chadwick wrote:
On Thu, Jul 17, 2008 at 12:20:42AM +0800, Eugene Grosbein wrote:
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source
Jeremy Chadwick wrote:
On Thu, Jul 17, 2008 at 12:20:42AM +0800, Eugene Grosbein wrote:
I fully understand and second efforts on educating people
how to configure BIND to be stong to attacks and keep them from using
query-source address with port option but how about
binding named to particular
On Wed, Jul 16, 2008 at 02:41:28PM -0700, Jo Rhett wrote:
On Jul 11, 2008, at 8:58 AM, Roland Smith wrote:
After about 2 weeks of watching it carefully I've learned almost
nothing. It's not a disk failure (AFAIK) it's not cpu overheat (now
running healthd without complaints) it's not based
2008/7/14 Sorin Pânca [EMAIL PROTECTED]:
I'm sorry for my late response, I was on vacation.
I think this was the case (although I thought we have only amd64 machines).
Is there a way to recover from this situation by ssh access only?
Thank you!
Sorin.
Chris Rees wrote:
Date: Mon, 23 Jun
On Wed, Jul 16, 2008 at 11:20:13PM +0100, Chris Rees wrote:
2008/7/14 Sorin Pânca [EMAIL PROTECTED]:
I'm sorry for my late response, I was on vacation.
I think this was the case (although I thought we have only amd64 machines).
Is there a way to recover from this situation by ssh access
I have a 64-bit system that had the 32-bit version of 6.3 installed on
it. Is it possible to use freebsd-update (or another somewhat
painless method) to switch the system to 64-bit?
We're running into the 4GB memory limit.
--Wade
___
Please try one of the more recent 7-stable snapshots
from June or July. They're located on the FTP sites
in /pub/FreeBSD/snapshots.
Best regards
Oliver
Adding :
set hint.apic.0.disabled=1
set hint.sio.0.disabled=1
set hint.sio.1.disabled=1
Did not help, I still got a hard reboot
I have a 64-bit system that had the 32-bit version of 6.3 installed on
it. Is it possible to use freebsd-update (or another somewhat
painless method) to switch the system to 64-bit?
We're running into the 4GB memory limit.
--Wade
I believe this is possible but you will come into a lot
We do such on our authoritative nameservers. The options we use:
listen-on { 127.0.0.1; 72.20.106.4; };
query-source address 72.20.106.4;
transfer-source 72.20.106.4;
notify-source 72.20.106.4;
interface-interval 0;
use-alt-transfer-source
Kevin K wrote:
I have a 64-bit system that had the 32-bit version of 6.3 installed on
it. Is it possible to use freebsd-update (or another somewhat
painless method) to switch the system to 64-bit?
We're running into the 4GB memory limit.
--Wade
FreeBSD-update is used for updates to binary
On Wed, Jul 16, 2008 at 5:40 PM, Jo Rhett [EMAIL PROTECTED] wrote:
On Jul 11, 2008, at 4:48 AM, Ronald Klop wrote:
You can try going into the kernel debugger to see where it is hanging.
Debugging via a serial cable is also very easy.
I don't know the details, but there is a lot of info in the
On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:
The 'query-source' options don't have to be specified: the system
will just choose some appropriate address according to the state of
the routing table. 'query-source' to set the source /IP/ is really
only useful in some
On Jul 16, 2008, at 8:51 PM, Eugene Grosbein wrote:
On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:
The 'query-source' options don't have to be specified: the system
will just choose some appropriate address according to the state of
the routing table. 'query-source' to set the
On Wed, Jul 16, 2008 at 09:06:33PM -0700, Chuck Swiger wrote:
On Jul 16, 2008, at 8:51 PM, Eugene Grosbein wrote:
On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:
The 'query-source' options don't have to be specified: the system
will just choose some appropriate address
Jeremy Chadwick wrote:
The config parms we use are necessary.
That's all you had to say. :) I see a lot of people attempt to
over-engineer stuff with named that leads to complications later. If
you are doing things for a good reason, keep doing them.
Doug
--
This .signature
--On July 16, 2008 9:06:33 PM -0700 Chuck Swiger [EMAIL PROTECTED] wrote:
On Jul 16, 2008, at 8:51 PM, Eugene Grosbein wrote:
On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:
The 'query-source' options don't have to be specified: the system
will just choose some appropriate
On Wed, 16 Jul 2008, Chuck Swiger wrote:
On Jul 16, 2008, at 8:51 PM, Eugene Grosbein wrote:
On Wed, Jul 16, 2008 at 06:34:38PM +0100, Matthew Seaman wrote:
The 'query-source' options don't have to be specified: the system
will just choose some appropriate address according to the state of
43 matches
Mail list logo
