Michael Peppler wrote:

> On Tue, 22 Jun 2004 02:07:49 -0700, Jan Franek wrote:
>
>
>>Jason L. Froebe wrote:
>>
>>
>>>Jan Franek wrote:
>>>
>>>
>>>
>>>>We use "ulimit -l xxxxx" to allow ASE to lock shared memory. This is
>>>>set in startup script running as root. It then starts startserver -f
>>>>RUN_xxx as sybase user. Child process inherits this limit so now we see
>>>>(cat /proc/xxx/status), that ASE has some memory locked.
>>>>
>>>>Jan
>>>
>>>
>>>Hi Jan,
>>>
>>>unfortunately "ulimit -l" only sets what *could* be locked in memory...
>>>it doesn't actually lock it (locking requires superuser priviledges).
>>>
>>>Jason
>>
>>Ha Jason,
>>
>>ulimit sets what could be locked and then ASE configured with "lock shared
>>memory" = 1 locks it.
>
>
> What does ipcs say?
>
> Michael

[root@obchod /]# ipcs -m -c

------ Shared Memory Segment Creators/Owners --------
shmid perms cuid cgid uid gid
45514752 600 sybase sybase sybase sybase

[root@obchod /]# ipcs -m -l

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 2636718
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

[root@obchod /]# ipcs -m -u

------ Shared Memory Status --------
segments allocated 1
pages allocated 512000
pages resident 512000
pages swapped 0
Swap performance: 0 attempts 0 successes

[root@obchod /]# ipcs -m -t

------ Shared Memory Attach/Detach/Change Times --------
shmid owner attached detached changed
45514752 sybase Jun 19 21:11:20 Jun 19 21:11:20 Jun 19
21:04:56

[root@obchod /]# ipcs -m -p

------ Shared Memory Creator/Last-op --------
shmid owner cpid lpid
45514752 sybase 28970 29004

Jan