On Tue, Nov 4, 2008 at 6:52 AM, Alex Zhang [EMAIL PROTECTED] wrote:
Hi buddy.
I'm a new comer and want to configure a Virtual server base on UNIX. The
safe, steady and easy for maintenance is needed.
Approximately 8GB memory will be mounted. Can anyone tell me how much memory
can
Hi buddy.
I'm a new comer and want to configure a Virtual server base on UNIX. The
safe, steady and easy for maintenance is needed.
Approximately 8GB memory will be mounted. Can anyone tell me how much memory
can be supported in FreeBSD?
Thanks.
BR
Alex
On Tue, Nov 04, 2008 at 09:52:20PM +0800, Alex Zhang wrote:
I'm a new comer and want to configure a Virtual server base on UNIX. The
safe, steady and easy for maintenance is needed.
Approximately 8GB memory will be mounted. Can anyone tell me how much memory
can be supported in FreeBSD
Hi Friends,
My name is Kamlesh and i am new to this group.
Could any one help me in Virtual Memory free space management: Splay tree to
Radix tree?
Thanks
Kamlesh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
I have STABLE-71 machine with 2GB memory and single 2GHz AMD3200 CPU.
There is one large active process slowly growing in memory from 500MB to
1300MB, not reading or writing any files.
There are many dormant processes almost not running at all.
Swap size remains constant (185MB). Total
On Tue, Oct 07, 2008 at 01:54:13PM -0700, Yuri wrote:
I have STABLE-71 machine with 2GB memory and single 2GHz AMD3200 CPU.
There is one large active process slowly growing in memory from 500MB to
1300MB, not reading or writing any files.
There are many dormant processes almost not running
Jeremy Chadwick wrote:
Regarding the memory bloat, what field in top(1) are you basing this
on?
For the total CPU usage I used
CPU: 100.0% user Active... all others were zeros.
For the process CPU I looked at WCPU.
Yuri
___
freebsd-questions
On Tue, Oct 07, 2008 at 04:43:09PM -0700, Yuri wrote:
Jeremy Chadwick wrote:
Regarding the memory bloat, what field in top(1) are you basing this
on?
For the total CPU usage I used
CPU: 100.0% user Active... all others were zeros.
For the process CPU I looked at WCPU.
I'm a little
Jeremy Chadwick wrote:
I'm a little confused. I was mainly referring to your statement:
There is one large active process slowly growing in memory from 500MB
to 1300MB, not reading or writing any files.
What field in top(1) were you looking at to determine this kind of
growth?
Sorry, I
On Tue, Oct 07, 2008 at 09:10:07PM -0700, Yuri wrote:
Jeremy Chadwick wrote:
I'm a little confused. I was mainly referring to your statement:
There is one large active process slowly growing in memory from 500MB
to 1300MB, not reading or writing any files.
What field in top(1) were you
Hi,
The top utility has SIZE and RES, but doesn't have what part of SIZE is
sysv shared memory. Is there something that can print out in detail how
a process uses / allocates its memory (I'm specifically interested in
sysvshm but there's also the stack mmap
In the last episode (Oct 01), Ivan Voras said:
Hi,
The top utility has SIZE and RES, but doesn't have what part of SIZE
is sysv shared memory. Is there something that can print out in
detail how a process uses / allocates its memory (I'm specifically
interested in sysvshm but there's also
Ivan Voras wrote:
2008/9/18 Ivan Voras [EMAIL PROTECTED]:
2008/9/18 Kris Kennaway [EMAIL PROTECTED]:
# Don't build modules with this kernel config, since they are not built
with
# the correct options headers.
makeoptions NO_MODULES=yes
wrong?
Not as such, but if you use buildkernel
Hello,
There is a peculiar case when physical memory limit is set through
hw.physmem and Freebsd sets usable memory to much lesser value.
In cases with 8 GB of RAM where the physical memory address space is
remapped above 4 GB and if we set hw.physmem to 4 GB then Freebsd actually
skips
Hello,
The error message: Can't create a new thread (errno 35); if you are not
out of available memory, you can consult the manual for a possible
OS-dependent bug
Our website started getting this error several weeks ago (when we
increased the number of application server machines connecting
Sam Nilsson wrote:
Hello,
The error message: Can't create a new thread (errno 35); if you are
not out of available memory, you can consult the manual for a possible
OS-dependent bug
Our website started getting this error several weeks ago (when we
increased the number of application server
On Tuesday 23 September 2008 12:13:58 Sam Nilsson wrote:
DB Servers: One Master, Two Read Only (replication)
4 GB of Memory on each server
FreeBSD 6.3-RELEASE-p3 FreeBSD 6.3-RELEASE-p3
MySQL 5.0.1
Here are some relevent items from my.cnf:
- set-variable = max_connections=1000
Vincent Hoffman wrote:
If you havent already, you could try increasing the per process memory
limit as per examples in
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-05/msg00258.html
(man tuning also says a bit about these tuneables but doesnt have the
examples that post does
2008/9/18 Ivan Voras [EMAIL PROTECTED]:
2008/9/18 Kris Kennaway [EMAIL PROTECTED]:
# Don't build modules with this kernel config, since they are not built
with
# the correct options headers.
makeoptions NO_MODULES=yes
wrong?
Not as such, but if you use buildkernel then modules
Hi,
I have some problem with physical memory being getting reported incorrectly
on Freebsd 6.3. I have 4GB of RAM installed but
BIOS call actually returns following usable physical memory map -
base address = 0, length = 640K
base address = 1M, length = 2.5G
base address = 4G, length = 5.5G
How
Ivan Voras wrote:
* Use a PAE kernel, which works fairly well, but doesn't support kernel
modules (if you are not familiar with kernel modules then you probably
don't need them so ignore this). There's a pre-packaged kernel
configuration named PAE for this.
PAE has supported kernel modules for
2008/9/18 Kris Kennaway [EMAIL PROTECTED]:
Ivan Voras wrote:
* Use a PAE kernel, which works fairly well, but doesn't support kernel
modules (if you are not familiar with kernel modules then you probably
don't need them so ignore this). There's a pre-packaged kernel
configuration named PAE
Ivan Voras wrote:
2008/9/18 Kris Kennaway [EMAIL PROTECTED]:
Ivan Voras wrote:
* Use a PAE kernel, which works fairly well, but doesn't support kernel
modules (if you are not familiar with kernel modules then you probably
don't need them so ignore this). There's a pre-packaged kernel
2008/9/18 Kris Kennaway [EMAIL PROTECTED]:
# Don't build modules with this kernel config, since they are not built
with
# the correct options headers.
makeoptions NO_MODULES=yes
wrong?
Not as such, but if you use buildkernel then modules *are* built with the
correct options
gahn wrote:
hello:
the machine i am using for freebsd has 4G memory. should i add follow lines
in my customized kernel file?:
# Compile acpi in statically since the module isn't built properly. Most
# machines which support large amounts of memory require acpi.
device acpi
hello:
the machine i am using for freebsd has 4G memory. should i add follow lines in
my customized kernel file?:
# Compile acpi in statically since the module isn't built properly. Most
# machines which support large amounts of memory require acpi.
device acpi
thanks
Polytropon [EMAIL PROTECTED] wrote:
Allthough fsck_ffs 5 does seem to be able to calloc() the needed
memory, it fails with the same message as fsck_ffs 7:
fsck_ffs: bad inode number 306176 to nextinode
Don't know what to do next. I may gather all information I
have, write
On Fri, 22 Aug 2008 10:29:05 +0200 (CEST), Oliver Fromme [EMAIL PROTECTED]
wrote:
Unfortunately fsck isn't able to cope with any arbitrary
level of damage. If certain kinds of unexpected problems
occur, it throws in the towel. In theory it might be
possible to deal with your particular
1073796864 bytes for inoinfo
#
So I examined /usr/src/sbin/fsck_ffs/pass1.c and found out
that a calloc() call caused the error; 1 GB was needed, but
2 GB were present in swap. Not enough?
Any suggestions what I could do to help fsck_ffs calloc()ing
the needed memory?
--
Polytropon
: cannot alloc 1073796864 bytes for inoinfo
#
So I examined /usr/src/sbin/fsck_ffs/pass1.c and found out
that a calloc() call caused the error; 1 GB was needed, but
2 GB were present in swap. Not enough?
Any suggestions what I could do to help fsck_ffs calloc()ing
the needed memory?
Increase
Polytropon [EMAIL PROTECTED] wrote:
On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway [EMAIL PROTECTED] wrote:
Increase kern.maxdsiz.
It seems that I don't have kern.maxdsiz:
# sysctl kern.maxdsiz
sysctl: unknown oid 'kern.maxdsiz'
Am I looking at the wrong
. 1.5 GB into the loader's config file
and that solved the problem. Thanks!
Best regards, and good luck with your recovery!
Allthough fsck_ffs 5 does seem to be able to calloc() the needed
memory, it fails with the same message as fsck_ffs 7:
fsck_ffs: bad inode number 306176 to nextinode
;
char *missatge = (char *)malloc(midataula * sizeof(char));
You should not cast the return value of malloc. [1]
missatge[0]='h';
missatge[1]='o';
missatge[2]='l';
missatge[3]='a';
Recall that malloc() makes no promises about the contents of the memory
Hi!
I have another problem trying to recover my data that has been destroyed
(in fact, it's just inaccessible because the inode at the entry od my
home directory died).
I'm using a dd image which reproduces the exact error of the defective
hard disk partition, I run fsck_ffs on a md type vnode.
Polytropon [EMAIL PROTECTED] writes:
I have another problem trying to recover my data that has been destroyed
(in fact, it's just inaccessible because the inode at the entry od my
home directory died).
I'm using a dd image which reproduces the exact error of the defective
hard disk
On Tue, 19 Aug 2008 14:45:18 -0400, Lowell Gilbert [EMAIL PROTECTED] wrote:
Polytropon [EMAIL PROTECTED] writes:
I always thought I needed to modify the
file system so fsck_ffs could do its job, now I think I rather would
modify fsck_ffs so it would skip these errors I can't see any reason
.
I've tried to reset all variables that i've seen in the sysctl -a list
refering to malloc, memory, mem, and so on... but so far i haven't fixed
the problem.
i'm running this script as root and in the /etc/login.conf file there's
only the default group with the unlimited values.
A part from
() is implicitly defined by the compiler as:
*
*int malloc(...);
*
* On a 64-bit machine converting a 64-bit pointer to `int' will
* lose the high-order 32 bits of the address, and you will try
* to access unexpected memory areas
* malloc() is implicitly defined by the compiler as:
*
*int malloc(...);
*
* On a 64-bit machine converting a 64-bit pointer to `int' will
* lose the high-order 32 bits of the address, and you will try
* to access unexpected memory
On Tue, 12 Aug 2008 18:22:21 +0200, Jordi Moles Blanco [EMAIL PROTECTED]
wrote:
Hello,
thank you very much for your time and help, i had completely
misunderstood how realloc() works.
You are welcome, of course :-)
___
freebsd-questions@freebsd.org
realloc(missatge, midataula * sizeof(char));
should be
missatge=realloc(missatge, midataula * sizeof(char));
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe,
and free work on the program's given data
area. This data area can be increased should there be a need for more
memory.
You should NEVER assume that memory blocks are contiguous. There are many
reasons why they would not be contiguous among them compiler
optimizations. If you really want
Hi All,
I am trying to validate my understanding of how malloc works by means
of the below C program which tries to corrupt essential information
maintained by malloc for free() operation.
The program allocates 4, 12 byte blocks (internally 16 bytes are allocated
for each 12 byte block).
On Tue, 5 Aug 2008 11:46:06 +0530, Shyamal Shukla [EMAIL PROTECTED] wrote:
Hi All,
I am trying to validate my understanding of how malloc works by means
of the below C program which tries to corrupt essential information
maintained by malloc for free() operation.
The program allocates 4, 12
On Tue, 05 Aug 2008 09:58:40 +0300, Giorgos Keramidas [EMAIL PROTECTED] wrote:
On Tue, 5 Aug 2008 11:46:06 +0530, Shyamal Shukla [EMAIL PROTECTED] wrote:
However, this does not happen. Can someone please correct my
understanding and provide me with a reference to the working of
malloc() and
Hello,
I am buying hardware for a FreeBSD server and me and my friend argue about
whether or not to by ECC RAM for the server. It is a HP ProLiant ML110 G4
machine and currently it has 2 x 512 HP DDR2 ECC memory.
My friend says buying ECC memory is not wise, because we would not profit from
Nejc Škoberne wrote:
4. If there is non-ECC memory installed, how does FreeBSD recognizes
(corrects?)
memory errors?
By crashing or corrupting data, of course. Not doing this is what ECC
is for :)
Kris
___
freebsd-questions@freebsd.org
Nejc Škoberne wrote:
Hello,
I am buying hardware for a FreeBSD server and me and my friend argue about
whether or not to by ECC RAM for the server. It is a HP ProLiant ML110 G4
machine and currently it has 2 x 512 HP DDR2 ECC memory.
My friend says buying ECC memory is not wise, because
4. If there is non-ECC memory installed, how does FreeBSD recognizes
(corrects?)
memory errors?
it's not OS job, but hardware.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe
DDR2 ECC memory.
My friend says buying ECC memory is not wise, because we would not profit
from it since this server will not need very high availability (but still
we'd like to make it a solid server). And also that ECC memory slows down
memory operations by 2-3% all together. Also, we
Michael Powell wrote:
[snip]
1. So, what would you base your decision on? Is getting ECC worth losing
1GB of non-ECC memory?
Oh - and the other criterion I forgot to mention. If the box in question is
only being used by 1 or 2 people and can have downtime to fix defects
whenever you want
Erik Trulsson wrote:
[snip]
No, non-ECC RAM cannot detect or correct any errors at all. (Old
parity-RAM could detect, but not correct, single-bit errors.)
Actually quite true. The old parity bit functionality that was removed from
RAM and then called non-ECC actually migrated to the memory
but the
system did not go down. I can shut it down and replace the memory at
my leisure.
A Solaris 10 server I run has a memory stick creating many errors.
System is still up and I can replace the stick when I can without a
hard crash.
ECC cannot necessarily protect you from every
that was removed from
RAM and then called non-ECC actually migrated to the memory controller.
So yes, it isn't the RAM that does it. Poor choice of wording on my part.
Not quite.
Old parity-RAM usually had an extra parity bit for every 8 data bits.
By computing the parity (odd or even number of 1s
Hi all,
I'm looking for methods to debug a kernel process memory overrun.
I'm working on an Ethernet driver for FreeBSD 7.0 and I'm facing a crash
after several (kldload + kldunload)s.
The exception is being thrown by the shell process after the last kldunload
successfully ends so I'm guessing
Hi,
I'm trying to get my 8 GB Sony MS card recognised by my fbsd 7.0-stable. But
when I'm putting the memory card in the reader, it doesn't even show up in
dmesg and there is no mention in /var/log/messages either. Reader and card are
working fine under windows.
Any pointers on how to get
Hi there,
I'm a novice in FreeBSD and I wanna know if there's some application to
automount my USB flash memory in FreeBSD 7.0.
Thanks,
--
Robe.
No se como será la tercera guerra mundial, sólo se que la cuarta será con
piedras y lanzas.
___
freebsd
On Thu, 10 Jul 2008 09:21:35 -0500
Robe [EMAIL PROTECTED] wrote:
Hi there,
I'm a novice in FreeBSD and I wanna know if there's some application
to automount my USB flash memory in FreeBSD 7.0.
Thanks,
Hi,
one way is amd.
Have a look at section 27.3.5 Automatic Mounts with
amd
1.24%
httpd
...etc...
As you can see there's plenty of free memory and the CPU is 70% idle
yet the load is sky high. When it's like this it's impossible to do
anything - every command can take anything from a few seconds to a
few minutes to respond - and the web user experience is shot
of free memory and the CPU is 70% idle
yet the load is sky high.
Well, load 10 isn't that much for a 4-way SMP system.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung
12592K devfs 1 0:00 2.19%
httpd
26791 80 1 -40 82376K 12636K devfs 0 0:00 1.85%
httpd
26783 80 1 -40 82392K 12640K devfs 3 0:00 1.84%
httpd
[...]
Please let vmstat 5 run for a minute ... Anything
that looks unusual?
procs memory page
2.19%
httpd
26791 80 1 -40 82376K 12636K devfs 0 0:00 1.85%
httpd
26783 80 1 -40 82392K 12640K devfs 3 0:00 1.84%
httpd
[...]
Please let vmstat 5 run for a minute ... Anything
that looks unusual?
procs memory pagedisks
for a minute ... Anything
that looks unusual?
procs memory pagedisks
faults cpu
r b w avm fre flt re pi po fr sr da0 pa0 in sy
cs us
sy id
1 412 2 8910132 2743568 2230 3 1 0 2106 93 0 0 1098 4733
3025 4
17 79
1 412 0
plenty of free memory and the CPU is 70% idle
yet the load is sky high. When it's like this it's impossible to do
anything - every command can take anything from a few seconds to a few
minutes to respond - and the web user experience is shot to pieces. I
can't find a reference that explains
and be able to store information quickly. I
| couldn't find much documentation on the memory limits in FreeBSD,
| especially per-process limits in both 32-bit and 64-bit versions.
| Could you please point me to where I can find such information along
| with other performance tuning tips
on the memory limits in FreeBSD,
especially per-process limits in both 32-bit and 64-bit versions.
Could you please point me to where I can find such information along
with other performance tuning tips and characteristics of the OS to
keep in mind
). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite
large;
on Linux it can be as much as 950 MB in resident memory, according
to
top. However, on FreeBSD I start to get ENOMEM always around the
time
my resident memory size is about 200 MB.
I read a few
Andrei Flame wrote:
pci10: mass storage at device 3.2 (no driver
attached)
This is, I am afraid, your card reader device :(
You're right about the device, thanks! My pciconf -lv
says:
[EMAIL PROTECTED]:10:3:2: class=0x018000 card=0x81ef104d
chip=0x803b104c rev=0x00
Hi,
I'm new on FreeBSD not on unix.
I want to mount automatically an usb-stick memory into my machine ?
I get some problems.
Need help.
- /etc/devfs.rules
add path 'da*' mode 0660 group operator
Actions:
1) ls -al /dev/da*
ls: No match.
2) I Plug into the USB port, the ImageMate 12-in-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nej ALL wrote:
Hi,
I'm new on FreeBSD not on unix.
I want to mount automatically an usb-stick memory into my machine ?
I get some problems.
Need help.
You're trying with your devfs stuff to create the file, but you have to realize
it's
Chuck Robey wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nej ALL wrote:
Hi,
I'm new on FreeBSD not on unix.
I want to mount automatically an usb-stick memory into my machine ?
I get some problems.
Need help.
You're trying with your devfs stuff to create the file, but you have
Hello Mark!
Mon, May 26, 2008 at 05:40:50AM +0100 you wrote:
It is detected as da2 and da3 (phone and memory stick - mine's a SCSI
system so da0 and da1 are the HDDs) but only the top-level device nodes
(/dev/da[23]) are created.
I can try to mount /dev/da3 until I'm blue in the face
I've just installed FreeBSD 7.0-RELEASE on my Sony
Vaio VGN-FE31ZR laptop with built-in memory stick duo
pro slot.
The problem is that I can't get memory stick card
detected and mounted. When I'm inserting a card,
nothing happens - no new messages in dmesg and
/var/log/messages, no /dev/da0
Andrei Flame wrote:
I've just installed FreeBSD 7.0-RELEASE on my Sony
Vaio VGN-FE31ZR laptop with built-in memory stick duo
pro slot.
The problem is that I can't get memory stick card
detected and mounted. When I'm inserting a card,
nothing happens - no new messages in dmesg and
/var/log
pci10: mass storage at device 3.2 (no driver
attached)
This is, I am afraid, your card reader device :(
You're right about the device, thanks! My pciconf -lv
says:
[EMAIL PROTECTED]:10:3:2: class=0x018000 card=0x81ef104d
chip=0x803b104c rev=0x00 hdr=0x00
vendor =
or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB in resident memory, according to
top. However, on FreeBSD I start to get ENOMEM always around the time
my resident memory size is about 200 MB.
I read
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB in resident memory, according to
top. However, on FreeBSD I start to get ENOMEM always around the time
my resident
but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB in resident memory, according to
top. However, on FreeBSD I start to get ENOMEM always around
PROTECTED]:
I have an application that runs on Linux or Mac OS X but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB in resident memory, according
PROTECTED] wrote:
In response to Brad Penoff [EMAIL PROTECTED]:
I have an application that runs on Linux or Mac OS X but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux
20, 2008 at 1:54 PM, Bill Moran
[EMAIL PROTECTED] wrote:
In response to Brad Penoff [EMAIL PROTECTED]:
I have an application that runs on Linux or Mac OS X but seems
to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the
memory
footprint for the application (osubw_sctpclien
Greetings,
I have an application that runs on Linux or Mac OS X but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB in resident memory, according to
top
In response to Brad Penoff [EMAIL PROTECTED]:
I have an application that runs on Linux or Mac OS X but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application (osubw_sctpclien below) is quite large;
on Linux it can be as much as 950 MB
On Tue, May 20, 2008 at 1:54 PM, Bill Moran [EMAIL PROTECTED] wrote:
In response to Brad Penoff [EMAIL PROTECTED]:
I have an application that runs on Linux or Mac OS X but seems to have
a problem when I run on FreeBSD (6.3 or 7). The issue is the memory
footprint for the application
However, I have read elsewhere that memory labeled as inactive should
be available for the heap
Is there a limit to how much memory may be allocated to a process?
Any other reasons someone might think of?
ulimit -a
___
freebsd-questions@freebsd.org
memory stick and use memdisk from
the syslinux package to load the image. A sample menu entry for grub
is included in the script.
http://borderworlds.dk/~xi/iso2diskimage.pl
--
Christian Laursen
___
freebsd-questions@freebsd.org mailing list
http
to represent evens).
Everything works great up until around 600 million, at which case
memory allocation fails. At this point, I am asking for 600M chars,
which is about 572MB (I might be failing to take account of offset?).
You are hitting the limit set as kern.maxdsiz (512 MB by default
, at which case
memory allocation fails. At this point, I am asking for 600M chars,
which is about 572MB (I might be failing to take account of offset?).
My system has about 2GB of memory. Top says: Mem: 159M Active, 1113M
Inact, 185M Wired, 56M Cache, 112M Buf, 481M Free.
From the man page, I am
I wrote my version a long time ago, I made it possible to split the set
of possible prime numbers in blocks of managable sizes to avoid this
problem :) this ofcourse made the algorithm somewhat slower. (Also I stored
the state of 8 odd numbers in one byte, reducing memory usage significantly
Hi,
Could someone please point me to information how to achieve this? Have
new hardware that lacks CD/floppy and want to install FreBSD...
Thanks,
--per
___
freebsd-questions@freebsd.org mailing list
-Original Message-
From: Mel [mailto:[EMAIL PROTECTED]
Sent: 15 April 2008 07:52 PM
To: freebsd-questions@freebsd.org
Cc: Vikash Badal
Subject: Re: How do I use more process memory with mysqld
On Tuesday 15 April 2008 17:07:14 Vikash Badal wrote:
datasize 33554432
On Wednesday 16 April 2008 10:08:44 Vikash Badal wrote:
-Original Message-
From: Mel [mailto:[EMAIL PROTECTED]
Sent: 15 April 2008 07:52 PM
To: freebsd-questions@freebsd.org
Cc: Vikash Badal
Subject: Re: How do I use more process memory with mysqld
On Tuesday 15 April 2008
Greetings,
I am trying to get mysql to use more memory, at present it seems stuck
at around 1G
From the mysql lists the it was suggested that I increase kern.maxdsiz,
kern.dfdl, kern.maxssiz
In /boot/loader.conf.
Having set the values of kern.maxdsiz and kern.dfdl mto 6G, I still
cant use
On Tuesday 15 April 2008 17:07:14 Vikash Badal wrote:
datasize 33554432 kB
That says 3G.
48647 mysql 35 200 963M 938M kserel 0 718.9H 22.17% mysqld
Your my.cnf is missing. Are you sure you're allowing mysql to go beyong 1G?
--
Mel
Problem with today's modular
but most software on the netboot clients (Apache,
Postfix) refuses to run without it.
On the 6.3 server rpc.lockd leaks memory, somewhat less than 1 meg per
hour. This means that every few days we need to restart the daemon. This
is quite annoying because we need to stop/start rpc.lockd on both
,
Postfix) refuses to run without it.
On the 6.3 server rpc.lockd leaks memory, somewhat less than 1 meg per
hour. This means that every few days we need to restart the daemon. This
is quite annoying because we need to stop/start rpc.lockd on both the
server and the clients in a controlled fashion
on the netboot
clients (Apache, Postfix) refuses to run without it.
On the 6.3 server rpc.lockd leaks memory, somewhat less than 1 meg per
hour. This means that every few days we need to restart the daemon. This
is quite annoying because we need to stop/start rpc.lockd on both the
server and the clients
with ulimit
on i386 - i don't know if 2 or 3GB is a limit.
on amd64 - essentially no limit
On Thu, 3 Apr 2008, Victor M. Blood wrote:
Hi, All.
How to allow ussage more than 2gb of memory on freebsd per process?
--
With all regards, Victor M. Blood. mailto: [EMAIL PROTECTED]
FTN: 2
On 03.04.2008, Wojciech Puchar wrote:
with ulimit
on i386 - i don't know if 2 or 3GB is a limit.
on amd64 - essentially no limit
ussage of amd is impossible, current machine is Intel Xeon.
--
With all regards, Victor M. Blood. mailto: [EMAIL PROTECTED]
FTN: 2:5024/[EMAIL PROTECTED],
On Thu, Apr 03, 2008 at 09:29:33AM CEST, Victor M. Blood [EMAIL PROTECTED]
said:
On 03.04.2008, Wojciech Puchar wrote:
with ulimit
on i386 - i don't know if 2 or 3GB is a limit.
on amd64 - essentially no limit
ussage of amd is impossible, current machine is Intel Xeon.
Intel 64 bit
401 - 500 of 1440 matches
Mail list logo
