On 14.10.2011 08:14, Hiroki Sato wrote:
> telnet www.freebsd.org 80 < /dev/null
[tykling@tykburk ~]$ telnet www.freebsd.org 80 < /dev/null
Trying 69.147.83.34...
Connected to red.freebsd.org.
Escape character is '^]'.
Connection closed by foreign host.
/Thomas
_
Thomas Steen Rasmussen wrote
in <4e97cffc.5020...@gibfest.dk>:
th> On 14.10.2011 02:52, Hiroki Sato wrote:
th> > Can you please send me the results of the following commands:
th>
th> Please see the output below each command. I forgot to
th> mention that the ipv6 uplink is a 6to4 tunnel, as you
On 14.10.2011 02:52, Hiroki Sato wrote:
> Can you please send me the results of the following commands:
Please see the output below each command. I forgot to
mention that the ipv6 uplink is a 6to4 tunnel, as you can
see below from the 2002: prefix.
>
> % ifconfig
[tykling@tykburk ~]$ ifconfig
Why not import daemontools? It's public domain these days. Pidfiles are a
hacky mess. UNIX already has a way to track processes which avoids all these
issues, with very little overhead.
Jos
___
freebsd-current@freebsd.org mailing list
http://lists.freebs
On 14 October 2011 02:40, Arnaud Lacombe wrote:
> Hi,
>
> On Thu, Oct 13, 2011 at 2:00 PM, wrote:
>> From: Arnaud Lacombe
>>
>> Hi folks,
>>
>> There is many case recently when I really wished timestamp were present in
>> the
>> post-mortem msgbuf. Such situation could be when userland applica
Thomas Steen Rasmussen wrote
in <4e9766c0.1020...@gibfest.dk>:
th> Hello list,
th>
th> I just upgraded my home workstation to 9.0-beta3 amd64. It seems
th> like my web browsers are preferring ipv4 over ipv6 after the upgrade,
th> I tested Firefox and Opera. After digging into rc.conf(5) I found
On 14.10.2011 00:31, Thomas Steen Rasmussen wrote:
> Hello list,
>
> I just upgraded my home workstation to 9.0-beta3 amd64. It seems
> like my web browsers are preferring ipv4 over ipv6 after the upgrade,
My laptop is also running 9.0-beta3 amd64 and I observe
the same behaviour there, so this do
Hello list,
I just upgraded my home workstation to 9.0-beta3 amd64. It seems
like my web browsers are preferring ipv4 over ipv6 after the upgrade,
I tested Firefox and Opera. After digging into rc.conf(5) I found this bit:
If ``AUTO'' is specified, it attempts to read a file
/etc/ip6add
On 10/12/2011 08:20, Michael Butler wrote:
> SVN r226302 solves the ichwd failure to attach issue ..
Still failing for me:
ichwd0: on isa0
ichwd0: unable to reserve GCS registers
device_attach: ichwd0 attach returned 6
r226340, smp, amd64
--
Nothin' ever doesn't change, but nothin'
On 10/12/2011 06:47, Ken Smith wrote:
> On Wed, 2011-10-12 at 14:39 +0100, Bruce Cran wrote:
>> On 29/09/2011 02:42, Ken Smith wrote:
>>> MD5 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) =
>>> 2ce7b93d28fd7ff37965893f1af3f7fc
>>> MD5 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = 4affc701f2052edc548274f090e49235
Hi,
On Thu, Oct 13, 2011 at 5:12 PM, Pegasus Mc Cleaft wrote:
> Hi Current,
>
> Should the new Beta 3 have "options COMPAT_FREEBSD8" in the GENERIC
> kernel config file? Or, does this happen when it goes RC?
>
What would you expect this option to cover ?
I'd assume that no ABI[0] have bee
Hi Current,
Should the new Beta 3 have "options COMPAT_FREEBSD8" in the GENERIC
kernel config file? Or, does this happen when it goes RC?
Ta
Peg
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
Hi,
On Thu, Oct 13, 2011 at 2:00 PM, wrote:
> From: Arnaud Lacombe
>
> Hi folks,
>
> There is many case recently when I really wished timestamp were present in the
> post-mortem msgbuf. Such situation could be when userland application segfault
> potentially triggering a panic/crash, or have in
From: Arnaud Lacombe
Hi folks,
There is many case recently when I really wished timestamp were present in the
post-mortem msgbuf. Such situation could be when userland application segfault
potentially triggering a panic/crash, or have information about the time-wise
location of a given message (
Adrian Chadd writes:
> Dag-Erling Smørgrav writes:
> > Could you check if network activity (e.g. downloading an ISO) triggers
> > it, and if so, if it goes away when you set the kern.eventtimer.idletick
> > sysctl to 0?
> Don't you mean 'set it to 1' ?
Uh, yes :)
DES
--
Dag-Erling Smørgrav - d
Nathan Whitehorn schreef:
On 10/13/11 04:25, O. Hartmann wrote:
On 10/13/11 10:39, Johan Hendriks wrote:
Hello all.
I just used the 9.0 B3 installer, and it defaults to GPT, which is
nice.
However, and there has been some discussions about it, it would be nice
if the installer warns me that
Here's something from a recentish -head. This is the same behaviour as
my beta2/beta3 boxes. This time, however, it's on a MIPS board.
It's quite possible this _isn't_ a USB problem but is a scsi or cam
layer problem.
The root is on /dev/da0, a USB device.
usbus0: 480Mbps High Speed USB v2.0
ug
In message <86lisp9dzn@ds4.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wr
ites:
>"Poul-Henning Kamp" writes:
>> For what it's worth, I regularly (=3Devery 10-12 days or so) see all
>> timer activity in the system die and have to use the 4-sec
>> power-switch to get the system down.
>
>Could
2011/10/13 Dag-Erling Smørgrav :
> "Poul-Henning Kamp" writes:
>> For what it's worth, I regularly (=every 10-12 days or so) see all
>> timer activity in the system die and have to use the 4-sec
>> power-switch to get the system down.
>
> Could you check if network activity (e.g. downloading an IS
"Poul-Henning Kamp" writes:
> For what it's worth, I regularly (=every 10-12 days or so) see all
> timer activity in the system die and have to use the 4-sec
> power-switch to get the system down.
Could you check if network activity (e.g. downloading an ISO) triggers
it, and if so, if it goes awa
Pawel Jakub Dawidek writes:
> I'm still in opinion that EWOULDBLOCK and EAGAIN (which is the same
> value on FreeBSD) should be converted to EEXIST on pidfile_open()
> return.
The historical (and documented) behavior is to return EAGAIN.
> Also if we now have for loop, why not to put count in th
On Thu, Oct 13, 2011 at 02:54:16PM +0200, Dag-Erling Smørgrav wrote:
> After discussing this with pjd@ on IRC, I arrived at the attached patch,
> which increases the length of time pidfile_open() itself waits (I hadn't
> noticed that it already looped) and sets *pidptr to -1 if it fails to read
> a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.10.2011 11:03, Peter Jeremy wrote:
>> I built world from SVN revision 226141. (...)
>
> r226141 is head. Did you build a 10-current or RELENG_9 world?
I built stable/9.
Sorry, the revision I mention is wrong because I have one checkout of
/ba
On 10/13/11 04:25, O. Hartmann wrote:
On 10/13/11 10:39, Johan Hendriks wrote:
Hello all.
I just used the 9.0 B3 installer, and it defaults to GPT, which is nice.
However, and there has been some discussions about it, it would be nice
if the installer warns me that i could get in trouble if i w
After discussing this with pjd@ on IRC, I arrived at the attached patch,
which increases the length of time pidfile_open() itself waits (I hadn't
noticed that it already looped) and sets *pidptr to -1 if it fails to read
a pid.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: lib/libutil/pidfile.
2011/10/13 Dag-Erling Smørgrav :
> Pawel Jakub Dawidek writes:
>> Dag-Erling Smørgrav writes:
>> > How do we fix this? My suggestion is to loop until pidfile_open()
>> > succeeds or errno != EAGAIN. Does anyone have any objections to that
>> > approach?
>> I think we already do that internally
In message <86lispaztm@ds4.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wr
ites:
>Dag-Erling Sm=C3=B8rgrav writes:
>> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
>> and KTR_SCHED enabled by default. I'll see what turns up. I'm also
>> going to try machdep.idle=3
Pawel Jakub Dawidek writes:
> Dag-Erling Smørgrav writes:
> > How do we fix this? My suggestion is to loop until pidfile_open()
> > succeeds or errno != EAGAIN. Does anyone have any objections to that
> > approach?
> I think we already do that internally in pidfile_open(). Can you take a look
On Thu, Oct 13, 2011 at 12:54:38PM +0200, Dag-Erling Smørgrav wrote:
> I looked at some of the programs that use pidfile(3) in base, and they
> pretty much all get it wrong. Consider these two scenarios:
>
> 1) common case
>
> process A process B
>
> main()
>
Dag-Erling Smørgrav writes:
> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR
> and KTR_SCHED enabled by default. I'll see what turns up. I'm also
> going to try machdep.idle=hlt with kern.eventtimer.idletick=0, and using
> a PCI re(4) instead of the on-board msk(4) whil
I looked at some of the programs that use pidfile(3) in base, and they
pretty much all get it wrong. Consider these two scenarios:
1) common case
process A process B
main()
pidfile_open() -> success
perform_initialization()
daemon()
pi
On 10/13/11 10:39, Johan Hendriks wrote:
Hello all.
I just used the 9.0 B3 installer, and it defaults to GPT, which is nice.
However, and there has been some discussions about it, it would be nice
if the installer warns me that i could get in trouble if i want to use
gmirror and the like.
Also
Hello all.
I just used the 9.0 B3 installer, and it defaults to GPT, which is nice.
However, and there has been some discussions about it, it would be nice
if the installer warns me that i could get in trouble if i want to use
gmirror and the like.
Also i find it a little strange that the def
On 2011-Oct-12 16:59:21 +0200, Jean-Sébastien Pédron
wrote:
>For a couple of days now, I can't boot FreeBSD 9-BETA3 on my laptop.
...
>I built world from SVN revision 226141. But now, kernel, zfsboot and
>zfsloader are those from 9.0-BETA3's DVD1. The zpool is version 28 and
>the zfs filesystems
On 13.10.11 00:33, Christoph Hoffmann wrote:
I am inclined to think that this is related to the way how we compile this code,
especially when run on the following particular processor:
1 Processor(s) detected, 4 total cores enabled, Hyperthreading is enabled
Proc 1: Intel(R) Xeon(R) CPU E5630
On Friday 07 October 2011 16:18:47 Niclas Zeising wrote:
> This might or might not be related, but, I'm having trouble with the iwn
> firmware crashing. I also have a clang built kernel (and userland)
> buildwith CPUTYPE=core2. My iwn device is
> iwn0: mem 0xe400-0xe4001fff irq
> 17 at devi
36 matches
Mail list logo
