Prev: How to boot from one of the miror disk?
Next: Monitor never blanks in Solaris 10
From: Vahid Moghaddasi on 9 Mar 2005 10:01
Hi,
I have a very strange problem for setting vmemory with "ulimit -v
size."
Here is the problem:
When I login to system and su - to another generic ID, I can only set
vmemory to 1048576 and if I use "ulimit -v 2097152" I will get:
ulimit: exceeds allowable limit error. But if I telnet/ssh to the box
directly as the generic user, I am able to do "ulimit -v 2097152"
Also, some users (on some systems) can set their ulimit -v to 2Gb and
some can not go beyond 1Gb.
Can someone please tell me why Solaris 9 is behaving like this and what
parameters can I modify to give unlimited vmemory to everyone, all the
times?
Thanks,
Vahid.

From: Chris Thompson on 9 Mar 2005 10:24
In article <1110378897.130897.217530(a)l41g2000cwc.googlegroups.com>,
Vahid Moghaddasi <vahid.moghaddasi(a)gmail.com> wrote:

>I have a very strange problem for setting vmemory with "ulimit -v
>size."
>Here is the problem:
>When I login to system and su - to another generic ID, I can only set
>vmemory to 1048576 and if I use "ulimit -v 2097152" I will get:
>ulimit: exceeds allowable limit error. But if I telnet/ssh to the box
>directly as the generic user, I am able to do "ulimit -v 2097152"

That is most easily explained by the first user (before the su) having
a hard limit of 1GB. su does not reset resource limits.

You should check the state of the hard limit with "ulimit -vH" as
well as the soft limit.

As to why the the first user has such a limit, you'll have to debug
that yourself. An obvious place to look is shell initialisation files
(/etc/profile, /etc/.login, ~/.profile, ~/.login, ...)

>Also, some users (on some systems) can set their ulimit -v to 2Gb and
>some can not go beyond 1Gb.

Same remarks apply. Maybe the different classes of users have different
login shells?

--
Chris Thompson
Email: cet1 [at] cam.ac.uk
From: Vahid Moghaddasi on 9 Mar 2005 11:58
Chris Thompson wrote:
> In article <1110378897.130897.217530(a)l41g2000cwc.googlegroups.com>,
> Vahid Moghaddasi <vahid.moghaddasi(a)gmail.com> wrote:
>
> >I have a very strange problem for setting vmemory with "ulimit -v
> >size."
> >Here is the problem:
> >When I login to system and su - to another generic ID, I can only
set
> >vmemory to 1048576 and if I use "ulimit -v 2097152" I will get:
> >ulimit: exceeds allowable limit error. But if I telnet/ssh to the
box
> >directly as the generic user, I am able to do "ulimit -v 2097152"
>
> That is most easily explained by the first user (before the su)
having
> a hard limit of 1GB. su does not reset resource limits.
>
> You should check the state of the hard limit with "ulimit -vH" as
> well as the soft limit.
>
> As to why the the first user has such a limit, you'll have to debug
> that yourself. An obvious place to look is shell initialisation files
> (/etc/profile, /etc/.login, ~/.profile, ~/.login, ...)
>
> >Also, some users (on some systems) can set their ulimit -v to 2Gb
and
> >some can not go beyond 1Gb.
>
> Same remarks apply. Maybe the different classes of users have
different
> login shells?

Thanks for your reply.
I had already checked the system as well as user profile and there is
no limits of any kind are set.
The problem is that we do not allow direct login as the generic ID so
they need to login as themselves and su to the generic ID. I checked
their profiles too but did not find any limit, yet some can only set
vmemory to 1GB and some to 2GB.
Would the way they login (telnet/ssh/rlogin) or terminal type matter?

>
> --
> Chris Thompson
> Email: cet1 [at] cam.ac.uk

From: Vahid Moghaddasi on 9 Mar 2005 21:38
Vahid Moghaddasi wrote:
> Chris Thompson wrote:
> > In article <1110378897.130897.217530(a)l41g2000cwc.googlegroups.com>,
> > Vahid Moghaddasi <vahid.moghaddasi(a)gmail.com> wrote:
> >
> > >I have a very strange problem for setting vmemory with "ulimit -v
> > >size."
> > >Here is the problem:
> > >When I login to system and su - to another generic ID, I can only
> set
> > >vmemory to 1048576 and if I use "ulimit -v 2097152" I will get:
> > >ulimit: exceeds allowable limit error. But if I telnet/ssh to the
> box
> > >directly as the generic user, I am able to do "ulimit -v 2097152"
> >
> > That is most easily explained by the first user (before the su)
> having
> > a hard limit of 1GB. su does not reset resource limits.
> >
> > You should check the state of the hard limit with "ulimit -vH" as
> > well as the soft limit.
> >
> > As to why the the first user has such a limit, you'll have to debug
> > that yourself. An obvious place to look is shell initialisation
files
> > (/etc/profile, /etc/.login, ~/.profile, ~/.login, ...)
> >
> > >Also, some users (on some systems) can set their ulimit -v to 2Gb
> and
> > >some can not go beyond 1Gb.
> >
> > Same remarks apply. Maybe the different classes of users have
> different
> > login shells?
>
Thanks for your reply.
I had already checked the system as well as user profile and there is
no limits of any kind are set.
The problem is that we do not allow direct login as the generic ID so
they need to login as themselves and su to the generic ID. I checked
their profiles too but did not find any limit, yet some can only set
vmemory to 1GB and some to 2GB.
Would the way they login (telnet/ssh/rlogin) or terminal type matter?

> >
> > --
> > Chris Thompson
> > Email: cet1 [at] cam.ac.uk

 | 
Pages: 1
Prev: How to boot from one of the miror disk?
Next: Monitor never blanks in Solaris 10