HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ulimit -a inside ksh script
Operating System - HP-UX
1826925
Members
2143
Online
109705
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-17-2008 12:04 PM
11-17-2008 12:04 PM
ulimit -a inside ksh script
Hi
If a run the ulimit -a command in a ksh script I've
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 65535
=> Not correct
But with command line it's correct:
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 65535
Any idea ?
Bests Regards
Den
If a run the ulimit -a command in a ksh script I've
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 65535
=> Not correct
But with command line it's correct:
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 65535
Any idea ?
Bests Regards
Den
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2008 12:31 PM
11-17-2008 12:31 PM
Re: ulimit -a inside ksh script
I can't see the script, I can't see which
shell you use interactively, and I can't see
your PATH, so I don't know which "ulimit"
you're using in each case. Knowing nothing,
I'd guess that "ulimit" is a shell built-in
in at least one of these situations. Or else
your PATH is different. Or both.
Something like "type ulimit", or "which
ulimit", or "whence ulimit", or similar, may
give you a clue.
"man" may also be informative.
shell you use interactively, and I can't see
your PATH, so I don't know which "ulimit"
you're using in each case. Knowing nothing,
I'd guess that "ulimit" is a shell built-in
in at least one of these situations. Or else
your PATH is different. Or both.
Something like "type ulimit", or "which
ulimit", or "whence ulimit", or similar, may
give you a clue.
"man
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2008 03:56 PM
11-17-2008 03:56 PM
Re: ulimit -a inside ksh script
>Not correct
It looks correct to me. It seems it is the output from /usr/bin/ulimit, not the ksh builtin (which doesn't have nofiles).
>But with command line it's correct:
This isn't correct since you can't be unlimited for data & stack.
It looks correct to me. It seems it is the output from /usr/bin/ulimit, not the ksh builtin (which doesn't have nofiles).
>But with command line it's correct:
This isn't correct since you can't be unlimited for data & stack.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP