Very Computer

by **Andrew Gide** » Tue, 15 Sep 1998 04:00:00

Under Solaris 2.6, the "Process Resource Limit Tunables" listed
in the result of sysdef seem to have changed format. These are
either very large, or negative, hex values now. In Solaris 2.5.1,
the values were either "normal" numbers or "Infinity".

How are lines like:

*
* Process Resource Limit Tunables (Current:Maximum)
*
ffffffff:fffffffd cpu time
ffffffff:fffffffd file size
ffffffff:fffffffd heap size
ffffffff:fffffffd stack size
0:7ffff000 core file size
ffffffff:fffffffd file descriptors
0: 800000 mapped memory

to be interpreted?

Thanks...

Andrew

by **Casper H.S. Dik - Network Security Engine** » Wed, 16 Sep 1998 04:00:00

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

>How are lines like:
>*
>* Process Resource Limit Tunables (Current:Maximum)
>*
>ffffffff:fffffffd cpu time
>ffffffff:fffffffd file size
>ffffffff:fffffffd heap size
>ffffffff:fffffffd stack size
> 0:7ffff000 core file size
>ffffffff:fffffffd file descriptors
> 0: 800000 mapped memory
>to be interpreted?

Not readily.

The rlimit values prior to 2.6 were unsigned 32 bit integrals.

The introduction of largefiles in 2.6 made it necessary to expand
the values to 64 bits.

Unfortnately, sysdef reads the kernel directly and so no type checking
is done. (For 32 bit programs, the limit values still compile as 32 bit values)

So sysdef now reads completely bogus information.

The first line is the soft CPU limit, the second the hard CPU limit,
followed by soft/hard filessize, soft/hard heap limit and last the
soft stack limit. The rest of the limits is not listed.

ffffffff:fffffffd is = (long long) -3 == RLIM_INFINITY

Casper

--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

by **Andrew Gide** » Wed, 16 Sep 1998 04:00:00

Quote:
>Unfortnately, sysdef reads the kernel directly and so no type checking
>is done. (For 32 bit programs, the limit values still compile as 32 bit values)

>So sysdef now reads completely bogus information.

So what sysdef displays as two 32 bit values is in fact
one 64 bit value. I understand.

Quote:
>The first line is the soft CPU limit, the second the hard CPU limit,
>followed by soft/hard filessize, soft/hard heap limit and last the
>soft stack limit. The rest of the limits is not listed.

So is there some other way to get the information not listed
by sysdef? Is it the same as that returned by ulimit?

Thanks...

Andrew

by **Casper H.S. Dik - Network Security Engine** » Thu, 17 Sep 1998 04:00:00

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

>So is there some other way to get the information not listed
>by sysdef? Is it the same as that returned by ulimit?

adb, I'm afraid.

In 2.7, there's "plimit 1" which should print what you want:

1: /etc/init -
resource current maximum
time(seconds) unlimited unlimited
file(blocks) unlimited unlimited
data(kbytes) unlimited unlimited
stack(kbytes) 8192 unlimited
coredump(blocks) unlimited unlimited
nofiles(descriptors) 64 1024
vmemory(kbytes) unlimited unlimited

--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Very Computer

Solaris 2.6 sysdef (vs. 2.5[.1])

Solaris 2.6 sysdef (vs. 2.5[.1])

Solaris 2.6 sysdef (vs. 2.5[.1])

Solaris 2.6 sysdef (vs. 2.5[.1])

Solaris 2.6 sysdef (vs. 2.5[.1])