https://community.hpe.com/t5/operating-system-hp-ux/globus-printer-shared-memory-error/m-p/3021230#M130482 hello,<BR />when i try to log on to GLOBUS, it bumps out and says "printer shared memory segment error PID****", i use HP-UX 11.0, i have tried removing the mem segment using this command.<BR /># ipcrm -m shmid<BR />and then when i try to log on again some more errors come on with different pid's, please what do i do?..i promise to award great points to whoever solves my problem. thanks.<BR />iphy Fri, 11 Jul 2003 10:10:27 GMT iphy onibuje 2003-07-11T10:10:27Z https://community.hpe.com/t5/operating-system-hp-ux/globus-printer-shared-memory-error/m-p/3021230#M130482 hello,<BR />when i try to log on to GLOBUS, it bumps out and says "printer shared memory segment error PID****", i use HP-UX 11.0, i have tried removing the mem segment using this command.<BR /># ipcrm -m shmid<BR />and then when i try to log on again some more errors come on with different pid's, please what do i do?..i promise to award great points to whoever solves my problem. thanks.<BR />iphy Fri, 11 Jul 2003 10:10:27 GMT https://community.hpe.com/t5/operating-system-hp-ux/globus-printer-shared-memory-error/m-p/3021230#M130482 iphy onibuje 2003-07-11T10:10:27Z https://community.hpe.com/t5/operating-system-hp-ux/globus-printer-shared-memory-error/m-p/3021231#M130483 Most likely, the GLOBUS code is only 32 bits and due to program crashes or bad use of the kill -9 command, the limited shared memory map has become fragmented. You can reboot and the problem will go away (for a while). The problem is that the programmer omitted very important information: the nature and size of the shared memory request which failed.<BR /><BR />However, is you get a copy of shminfo from: ftp:/contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo/ you can see the fragmentation. Fri, 11 Jul 2003 10:40:28 GMT https://community.hpe.com/t5/operating-system-hp-ux/globus-printer-shared-memory-error/m-p/3021231#M130483 Bill Hassell 2003-07-11T10:40:28Z