- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cannot raise "ulimit -d": not owner
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 04:08 AM
12-06-2004 04:08 AM
Cannot raise "ulimit -d": not owner
Malloc is out of memory, leaks over 512k:
/usr/ccs/bin/ld: Out of memory
Malloc: 98171872 bytes allocated by Unknown:0x3a0b7
Malloc: 1064960 bytes allocated by Unknown:0x38083
I assume I would need to increase the data segment size (ulimit -d), as it's currently set as follows:
data seg size (kbytes) 180224
However, I can not change the value to any other number, I always get "bash: ulimit: cannot modify limit: Not owner". There is no /etc/profile or any other dot file in $HOME that is messing with the ulimits. I already reconfigured the kernel to the following value (from /stand/system):
maxdsiz 0X0B000000
How come that this value is not propagated to my user account? Any suggestions would be appreciated. Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 04:38 AM
12-06-2004 04:38 AM
Re: Cannot raise "ulimit -d": not owner
http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1102354491264+28353475&threadId=87639
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=439475
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 04:39 AM
12-06-2004 04:39 AM
Re: Cannot raise "ulimit -d": not owner
This issue may not be what we think.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 05:23 AM
12-06-2004 05:23 AM
Re: Cannot raise "ulimit -d": not owner
Maybe this link from itrc would help,
http://www1.itrc.hp.com/service/cki/search.do?category=c0&mode=id&searchString=3200185478&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
The doc id is 3200185478.
The solution was adding some swap space.
hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 06:04 AM
12-06-2004 06:04 AM
Re: Cannot raise "ulimit -d": not owner
B. To see you limits:
# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 244140
stack(kbytes) 12288
memory(kbytes) unlimited
coredump(blocks) 4194303
C. To set your own limits:
ulimit -d 100000 Where 100000 is < 244140
D. To Fix "oracle" ID limits:
1. Log in as root.
2. Use ulimit() to check settings:
# ulimit -a
3. Reset ulimit() to its maximum value:
# ulimit -d 65536 oracle
4. Have the Oracle user log off and back on.
E. NOTE: See the manual page for sh-posix(1) for information
about ulimit().
F. The .proto file sets up the ulimit.
I don't understand how it works.
cat /var/adm/cron/.proto
# @(#) $Revision: 27.1 $
cd $d
ulimit $l
umask $m
$<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 06:58 PM
12-06-2004 06:58 PM
Re: Cannot raise "ulimit -d": not owner
The full output of "ulimit -Sa" for this user:
core file size (blocks) 2097151
data seg size (kbytes) 180224
file size (blocks) unlimited
max memory size (kbytes) unlimited
open files 4096
pipe size (512 bytes) 16
stack size (kbytes) 70656
cpu time (seconds) unlimited
max user processes 201
virtual memory (kbytes) unlimited
"ulimit -Ha" reports:
core file size (blocks) unlimited
data seg size (kbytes) 180224
file size (blocks) unlimited
max memory size (kbytes) unlimited
open files 4096
pipe size (512 bytes) 16
stack size (kbytes) 70656
cpu time (seconds) unlimited
max user processes 201
virtual memory (kbytes) unlimited
I will take a look at the other suggestions made in this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 07:07 PM
12-06-2004 07:07 PM
Re: Cannot raise "ulimit -d": not owner
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1024 0 1024 0% 0 - 1 /dev/vg00/lvol2
dev 2048 0 2048 0% 0 - 0 /dev/vg00/swap
reserve - 98 -98
memory 1535 1057 478 69%
total 4607 1155 3452 25% - 0 -
bash-2.05$ grep -i maxssiz /stand/system
maxssiz 0X04500000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 07:33 PM
12-06-2004 07:33 PM
Re: Cannot raise "ulimit -d": not owner
My apologies for wasting your time on something as trivial as this...
"ulimit -d" reports 180224 kbytes. The value "maxdsiz" was set to "0X0B000000" (in bytes), which are exactly 180224 kbytes...
Duh!
Raising the maxdsiz value a bit more (now to "0X20000000") also affects the ulimit:
data seg size (kbytes) 524288
Consider this case closed - this was a pilot error :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2004 07:34 PM
12-06-2004 07:34 PM