Post-installation wizard on domain lookup daemon

Hi,
the post-installation wizard asks whether or not to activate the domain lookup daemon at a certain step. However, it says that activating it may cost about 35 MByte of RAM (if I recall correctly), but it actually uses 76 MByte on a freshly set up Debian 6 virtual server. This is more than twice as much. Hence, this statement should be adjusted.

Best regards,
fuggi

Status: 
Closed (fixed)

Comments

Ah ... sorry! I missed a column. Anyway, 47 MByte is significantly more than 35 MByte on a low memory system.

Howdy -- what are the output of the following commands on your system:

ldd /bin/ls
uname -a

That will provide some input on your architecture.

ldd /bin/ls:

linux-vdso.so.1 => (0x00007ffffddfd000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00002ad412bfd000)
librt.so.1 => /lib/librt.so.1 (0x00002ad412e1b000)
libacl.so.1 => /lib/libacl.so.1 (0x00002ad413024000)
libc.so.6 => /lib/libc.so.6 (0x00002ad41322b000)
libdl.so.2 => /lib/libdl.so.2 (0x00002ad41358d000)
/lib64/ld-linux-x86-64.so.2 (0x00002ad4129dd000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00002ad413792000)
libattr.so.1 => /lib/libattr.so.1 (0x00002ad4139ae000)

uname -a:

Linux [hostname] 2.6.32-028stab092.1 #1 SMP Wed Jul 20 19:47:12 MSD 2011 x86_64 GNU/Linux

Looks like a 64-bit system - which often means that memory usage is doubled. On my test 32-bit systems, lookup-domain-daemon only consumes 37 MB.

It is well known that memory usage on 64 bit systems is higher than on 32 bit systems. But it can't be taken for granted that the wizard refers only to 32 bit systems, particularly not on a 64 bit machine.

I will correct these memory estimates in the next Virtualmin release to take architecture into account.

Automatically closed -- issue fixed for 2 weeks with no activity.