[hobbit] MAX_DATA hard coded somewhere? <= was: oversized [ports] section

[Henrik Stoerner]

On Tue, Aug 08, 2006 at 10:56:15AM -0400, Jerry Yu wrote:
> I bumped up the MAXMSG_DATA and MAXMSG_STATUS again, to 768 from 512
> (was 256 by default). restarted hobbit ok. the list of SHM via ipcs
> (appended below)
> shows the 768K segment is created. However, an hour later, I still ran
> into messages for hobbitd like this:
> Oversize data/client msg from 10.77.9.106 truncated (n=722041, limit 524288)

> ------ Shared Memory Segments --------
> key        shmid      owner      perms      bytes      nattch     status
> 0x0101f2e0 2129920    hobbit    600        786432     2
> 0x0201f2e0 2162689    hobbit    600        786432     2
> 0x0301f2e0 2195458    hobbit    600        786432     2
> 0x0401f2e0 2228227    hobbit    600        262144     2
> 0x0501f2e0 2260996    hobbit    600        262144     1
> 0x0601f2e0 2293765    hobbit    600        32768      1
> 0x0701f2e0 2326534    hobbit    600        524288     2
> 0x0801f2e0 2359303    hobbit    600        524288     2

These ipcs numbers show that your current settings are:

MAXMSG_STATUS=768
MAXMSG_STACHG=768 (matches the _STATUS value)
MAXMSG_PAGE=768 (ditto)
MAXMSG_DATA=256
MAXMSG_NOTES=256
MAXMSG_ENADIS=32
MAXMSG_CLIENT=512
MAXMSH_CLICHG=512 (matches the _CLIENT setting)

>> ---- "hobbitservers.cfg"---cut----
> MAXMSG_CLIENT = 1024
> MAXMSG_DATA = 768
> MAXMSG_STATUS=768

Hmm - try removing that space around the '=' sign:

MAXMSG_CLIENT=1024
MAXMSG_DATA=768
MAXMSG_STATUS=768

I think that's the problem.


Regards,
Henrik