SEO

Hi,

I would like to knwo how I must set the parameters in Informix 7.31.

On my log file appears the message:

08:56:25 Dynamically allocated new message shared memory segment (size
352KB)
08:56:25 Requested shared memory segment size rounded from 344KB to
352KB
08:56:25 Requested shared memory segment size rounded from 344KB to
352KB


For more information my /ets/system file is:

informix@BO:/$ more /etc/system
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*

* moddir:
*
* Set the search path for modules. This has a format similar to
the
* csh path variable. If the module isn't found in the first
directory
* it tries the second and so on. The default is /kernel
/usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules



* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)



* exclude:
*
* Modules appearing in the moddir path which are NOT to be
loaded,
* even if referenced. Note that `exclude' accepts either a module
name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys



* forceload:
*
* Cause these modules to be loaded at boot time, (just before
mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it
will
* be installed.
*
* Example:
* forceload: drv/foo



* set:
*
* Set an integer variable in the kernel or a module to a new
value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named
'test_module'
*
* set test_module:debug = 0x13
set shmsys:shminfo_shmmax=256000000
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=100

set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=512

set msgsys:msginfo_msgmni=2048


#set semsys:seminfo_semmap=50
#set semsys:seminfo_semmni=2000
#set semsys:seminfo_semmns=2000
#set semsys:seminfo_semmnu=500
#set semsys:seminfo_semmsl=512
set semsys:seminfo_semopm=256
#set semsys:seminfo_semume=500
set semsys:seminfo_semvmx=32767
set semsys:seminfo_semaem=16384
#set shmsys:shminfo_shmmax=20971520
#set shmsys:shminfo_shmmin=0
#set shmsys:shminfo_shmmni=2000
#set shmsys:shminfo_shmseg=100
#set msgsys:msginfo_msgmni=2048
set max_nprocs=1000
set fnsod:sod_Debug=0
set rlim_fd_max=1024
set rlim_fd_cur=256

* vxvm_START (do not remove)
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
forceload: drv/dad
forceload: drv/pcipsy
forceload: drv/sd
forceload: drv/ssd
rootdev:/pseudo/vxio@0:0
set vxio:vol_rootdev_is_volume=1
*/dev/console 0666 /dev/console
* vxvm_END (do not remove)

Any idea of how to configure that parameters?

Thank you.

Alan

please, show your onconfig file and the output of 'onstat -g seg'

Ruediger

Massoroto wrote:
> Hi,
>
> I would like to knwo how I must set the parameters in Informix 7.31.
>
> On my log file appears the message:
>
> 08:56:25 Dynamically allocated new message shared memory segment (size
> 352KB)
> 08:56:25 Requested shared memory segment size rounded from 344KB to
> 352KB
> 08:56:25 Requested shared memory segment size rounded from 344KB to
> 352KB
>
>
> For more information my /ets/system file is:
>
> informix@BO:/$ more /etc/system
> *ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
> *
> * SYSTEM SPECIFICATION FILE
> *
>
> * moddir:
> *
> * Set the search path for modules. This has a format similar to
> the
> * csh path variable. If the module isn't found in the first
> directory
> * it tries the second and so on. The default is /kernel
> /usr/kernel
> *
> * Example:
> * moddir: /kernel /usr/kernel /other/modules
>
>
>
> * root device and root filesystem configuration:
> *
> * The following may be used to override the defaults provided by
> * the boot program:
> *
> * rootfs: Set the filesystem type of the root.
> *
> * rootdev: Set the root device. This should be a fully
> * expanded physical pathname. The default is the
> * physical pathname of the device where the boot
> * program resides. The physical pathname is
> * highly platform and configuration dependent.
> *
> * Example:
> * rootfs:ufs
> * rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
> *
> * (Swap device configuration should be specified in /etc/vfstab.)
>
>
>
> * exclude:
> *
> * Modules appearing in the moddir path which are NOT to be
> loaded,
> * even if referenced. Note that `exclude' accepts either a module
> name,
> * or a filename which includes the directory.
> *
> * Examples:
> * exclude: win
> * exclude: sys/shmsys
>
>
>
> * forceload:
> *
> * Cause these modules to be loaded at boot time, (just before
> mounting
> * the root filesystem) rather than at first reference. Note that
> * forceload expects a filename which includes the directory. Also
> * note that loading a module does not necessarily imply that it
> will
> * be installed.
> *
> * Example:
> * forceload: drv/foo
>
>
>
> * set:
> *
> * Set an integer variable in the kernel or a module to a new
> value.
> * This facility should be used with caution. See system(4).
> *
> * Examples:
> *
> * To set variables in 'unix':
> *
> * set nautopush=32
> * set maxusers=40
> *
> * To set a variable named 'debug' in the module named
> 'test_module'
> *
> * set test_module:debug = 0x13
> set shmsys:shminfo_shmmax=256000000
> set shmsys:shminfo_shmmin=100
> set shmsys:shminfo_shmmni=100
> set shmsys:shminfo_shmseg=100
>
> set semsys:seminfo_semmap=64
> set semsys:seminfo_semmni=4096
> set semsys:seminfo_semmns=4096
> set semsys:seminfo_semmnu=4096
> set semsys:seminfo_semume=64
> set semsys:seminfo_semmsl=512
>
> set msgsys:msginfo_msgmni=2048
>
>
> #set semsys:seminfo_semmap=50
> #set semsys:seminfo_semmni=2000
> #set semsys:seminfo_semmns=2000
> #set semsys:seminfo_semmnu=500
> #set semsys:seminfo_semmsl=512
> set semsys:seminfo_semopm=256
> #set semsys:seminfo_semume=500
> set semsys:seminfo_semvmx=32767
> set semsys:seminfo_semaem=16384
> #set shmsys:shminfo_shmmax=20971520
> #set shmsys:shminfo_shmmin=0
> #set shmsys:shminfo_shmmni=2000
> #set shmsys:shminfo_shmseg=100
> #set msgsys:msginfo_msgmni=2048
> set max_nprocs=1000
> set fnsod:sod_Debug=0
> set rlim_fd_max=1024
> set rlim_fd_cur=256
>
> * vxvm_START (do not remove)
> forceload: drv/vxdmp
> forceload: drv/vxio
> forceload: drv/vxspec
> forceload: drv/dad
> forceload: drv/pcipsy
> forceload: drv/sd
> forceload: drv/ssd
> rootdev:/pseudo/vxio@0:0
> set vxio:vol_rootdev_is_volume=1
> */dev/console 0666 /dev/console
> * vxvm_END (do not remove)
>
> Any idea of how to configure that parameters?
>
> Thank you.
>
> Alan

please, show your onconfig file and the output of 'onstat -g seg'

Ruediger

Massoroto wrote:
> Hi,
>
> I would like to knwo how I must set the parameters in Informix 7.31.
>
> On my log file appears the message:
>
> 08:56:25 Dynamically allocated new message shared memory segment (size
> 352KB)
> 08:56:25 Requested shared memory segment size rounded from 344KB to
> 352KB
> 08:56:25 Requested shared memory segment size rounded from 344KB to
> 352KB
>
>
> For more information my /ets/system file is:
>
> informix@BO:/$ more /etc/system
> *ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
> *
> * SYSTEM SPECIFICATION FILE
> *
>
> * moddir:
> *
> * Set the search path for modules. This has a format similar to
> the
> * csh path variable. If the module isn't found in the first
> directory
> * it tries the second and so on. The default is /kernel
> /usr/kernel
> *
> * Example:
> * moddir: /kernel /usr/kernel /other/modules
>
>
>
> * root device and root filesystem configuration:
> *
> * The following may be used to override the defaults provided by
> * the boot program:
> *
> * rootfs: Set the filesystem type of the root.
> *
> * rootdev: Set the root device. This should be a fully
> * expanded physical pathname. The default is the
> * physical pathname of the device where the boot
> * program resides. The physical pathname is
> * highly platform and configuration dependent.
> *
> * Example:
> * rootfs:ufs
> * rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
> *
> * (Swap device configuration should be specified in /etc/vfstab.)
>
>
>
> * exclude:
> *
> * Modules appearing in the moddir path which are NOT to be
> loaded,
> * even if referenced. Note that `exclude' accepts either a module
> name,
> * or a filename which includes the directory.
> *
> * Examples:
> * exclude: win
> * exclude: sys/shmsys
>
>
>
> * forceload:
> *
> * Cause these modules to be loaded at boot time, (just before
> mounting
> * the root filesystem) rather than at first reference. Note that
> * forceload expects a filename which includes the directory. Also
> * note that loading a module does not necessarily imply that it
> will
> * be installed.
> *
> * Example:
> * forceload: drv/foo
>
>
>
> * set:
> *
> * Set an integer variable in the kernel or a module to a new
> value.
> * This facility should be used with caution. See system(4).
> *
> * Examples:
> *
> * To set variables in 'unix':
> *
> * set nautopush=32
> * set maxusers=40
> *
> * To set a variable named 'debug' in the module named
> 'test_module'
> *
> * set test_module:debug = 0x13
> set shmsys:shminfo_shmmax=256000000
> set shmsys:shminfo_shmmin=100
> set shmsys:shminfo_shmmni=100
> set shmsys:shminfo_shmseg=100
>
> set semsys:seminfo_semmap=64
> set semsys:seminfo_semmni=4096
> set semsys:seminfo_semmns=4096
> set semsys:seminfo_semmnu=4096
> set semsys:seminfo_semume=64
> set semsys:seminfo_semmsl=512
>
> set msgsys:msginfo_msgmni=2048
>
>
> #set semsys:seminfo_semmap=50
> #set semsys:seminfo_semmni=2000
> #set semsys:seminfo_semmns=2000
> #set semsys:seminfo_semmnu=500
> #set semsys:seminfo_semmsl=512
> set semsys:seminfo_semopm=256
> #set semsys:seminfo_semume=500
> set semsys:seminfo_semvmx=32767
> set semsys:seminfo_semaem=16384
> #set shmsys:shminfo_shmmax=20971520
> #set shmsys:shminfo_shmmin=0
> #set shmsys:shminfo_shmmni=2000
> #set shmsys:shminfo_shmseg=100
> #set msgsys:msginfo_msgmni=2048
> set max_nprocs=1000
> set fnsod:sod_Debug=0
> set rlim_fd_max=1024
> set rlim_fd_cur=256
>
> * vxvm_START (do not remove)
> forceload: drv/vxdmp
> forceload: drv/vxio
> forceload: drv/vxspec
> forceload: drv/dad
> forceload: drv/pcipsy
> forceload: drv/sd
> forceload: drv/ssd
> rootdev:/pseudo/vxio@0:0
> set vxio:vol_rootdev_is_volume=1
> */dev/console 0666 /dev/console
> * vxvm_END (do not remove)
>
> Any idea of how to configure that parameters?
>
> Thank you.
>
> Alan