Brandon Falk wrote:
The simple program:
int main()
{
puts("Apple cider");
Yields the following result in valgrind:
==4703== HEAP SUMMARY:
==4703== in use at exit: 4,096 bytes in 1 blocks
==4703== total heap usage: 1 allocs, 0 frees, 4,096 bytes allocated
==4703==
==4703==
that s why I 've been so in doubt using freebsd AMD64 release.
On 28/01/2010 1:05 PM, Sherin George wrote:
Hello Sam,
The problem happened today again.
I am getting this message on traceroute
===
traceroute: findsaddr: write: No such process
When running a ping t
Hello,
Thanks Qing.
I have already upgraded to latest patch as per per the advise of
"freebsd-hackers"
==
myserver# uname -a
FreeBSD myserver.server.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue
Jan 5 21:11:58 UTC 2010
r...@amd64-builder.daemonology.net:/usr/obj
I have been consumed by day job 200% of my time.
I have some free time tonight and can work with you off-line.
Is it possible for you to update to the latest stable-8 kernel
and we start from there ?
-- Qing
-Original Message-
From: owner-freebsd-...@freebsd.org on behalf of Sherin Ge
Hello Sam,
The problem happened today again.
I am getting this message on traceroute
===
traceroute: findsaddr: write: No such process
When running a ping to 8.8.8.8, it says following.
===
ping: sendto: No route to host
Please
On Wednesday 27 January 2010 4:47:55 pm Kostik Belousov wrote:
> On Wed, Jan 27, 2010 at 04:10:33PM -0500, John Baldwin wrote:
> > I'm not aware of a portable way to obtain this information across all UNIX
> > variants. For FreeBSD, there isn't a way for userland to obtain the list
> > of filesyst
On Wed, Jan 27, 2010 at 04:10:33PM -0500, John Baldwin wrote:
> I'm not aware of a portable way to obtain this information across all UNIX
> variants. For FreeBSD, there isn't a way for userland to obtain the list
> of filesystems cleanly. The patch looks good to me. I'll probably commit it
> af
Hi. we're using a 7.2 box as a firewall/nat/ipsec machine with ipfilter/ipnat
and ipsec-tools
This box is crashing a lot, and all the panics are identical:
r...@firewall /var/crash]# uname -a
FreeBSD firewall. 7.2-RELEASE-p5 FreeBSD 7.2-RELEASE-p5 #3: Mon Dec 28
16:45:47 ART 2009 r...@firewa
On Wednesday 27 January 2010 3:32:17 pm Fernando Apesteguía wrote:
> 2010/1/27 John Baldwin :
> > On Tuesday 26 January 2010 4:52:35 pm Fernando Apesteguía wrote:
> >> 2010/1/15 John Baldwin :
> >> > On Friday 08 January 2010 12:19:29 pm Fernando Apesteguía wrote:
> >> >> Hi all,
> >> >>
> >> >> Th
2010/1/27 John Baldwin :
> On Tuesday 26 January 2010 4:52:35 pm Fernando Apesteguía wrote:
>> 2010/1/15 John Baldwin :
>> > On Friday 08 January 2010 12:19:29 pm Fernando Apesteguía wrote:
>> >> Hi all,
>> >>
>> >> This patch implements the "filesystems" file in the linux proc fs.
>> >> I have use
On Wed, 27 Jan 2010 08:18:43 -0600
Brandon Falk wrote:
> The simple program:
>
> #include
> #include
>
> int main()
> {
> puts("Apple cider");
> return 0;
> }
>
> Yields the following result in valgrind:
>
> ==4703== Memcheck, a memory error detector
> ==4703== Copyright (C)
On Tuesday 26 January 2010 4:52:35 pm Fernando Apesteguía wrote:
> 2010/1/15 John Baldwin :
> > On Friday 08 January 2010 12:19:29 pm Fernando Apesteguía wrote:
> >> Hi all,
> >>
> >> This patch implements the "filesystems" file in the linux proc fs.
> >> I have used it for some time without seeing
The simple program:
#include
#include
int main()
{
puts("Apple cider");
return 0;
}
Yields the following result in valgrind:
==4703== Memcheck, a memory error detector
==4703== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==4703== Using Valgrind-3.5.0 and Lib
Alexander Best wrote:
> i believe the sound you hear is due to the emergency unload sequence.
> i'm not 100% sure, but i think after applying the patch the sound
> is gone. i recently replaced my old IDE hdd (which made a very loud
> "click!" during shutdown) with a new SATA hdd. the new one i
2010/1/27 Oliver Fromme :
> Second, you should make sure that ATA_STANDBY_IMMEDIATE is
> only used when a poweroff is requested, but not in other
> cases. Of course, ATA_FLUSHCACHE should *always* be sent.
Would SLEEP not be a better option than STANBY IMMEDIATE, as SLEEP
actually turns the disk
Alexander Best wrote:
> because of kern/140752 i looked through a discussion back in 2009
> (http://lists.freebsd.org/pipermail/freebsd-hackers/2009-March/027879.html)
> concerning freebsd's hdd spin down procedure. right now ATA_FLUSHCACHE is
> being used although the hitachi hdd specs refere
On Tue, 26 Jan 2010 20:17:23 +0100 (CET)
Alexander Best wrote:
> hi there,
>
> because of kern/140752 i looked through a discussion back in 2009
> (http://lists.freebsd.org/pipermail/freebsd-hackers/2009-March/027879.html)
> concerning freebsd's hdd spin down procedure. right now ATA_FLUSHCACHE
i believe the sound you hear is due to the emergency unload sequence. i'm not
100% sure, but i think after applying the patch the sound is gone. i recently
replaced my old IDE hdd (which made a very loud "click!" during shutdown) with
a new SATA hdd. the new one is very quiet and so it's not that e
18 matches
Mail list logo
