The OS is FreeBSD here are the results of limit -a (limit is the same as
ulimit in FreeBSD)
Telnet session:
limits -a
Resource limits (current):
cputime infinity secs
filesize infinity kb
datasize 2048000 kb
stacksize 65536 kb
coredumpsize infinity kb
memoryuse infinity kb
memorylocked infinity kb
maxprocesses 2067
openfiles 4136
Ssh2 Session:
limits -a
Resource limits (current):
cputime infinity secs
filesize infinity kb
datasize 32768 kb
stacksize 16384 kb
coredumpsize 0 kb
memoryuse-cur 65536 kb
memorylocked-cur 65536 kb
maxprocesses 256
openfiles 1024
Definite limits with Ssh2 on datasize, stacksize, coredumpsize,
memoryuse-cur, memorylocked-cur, maxprocesses and openfiles.
Now how can this be changed so I can give the same limits to my users?
Jorge
On Sat, 19 Feb 2000, Garance A Drosihn wrote:
> At 6:49 PM -0800 2/18/00, Jorge Aldana wrote:
> >Hello fellow ssh2 users,
> >
> >I'm having an odd problem, basically a user attempts to run a program
> >which attempts to alocation lots of RAM and temporary disk space and ssh
> >does not allow the user to do this. Is there any limitations within ssh
> >that would restrict large programs from running or allocation space and if
> >so how can they be changed?
>
> It might be that the system you're connecting to has different
> user-classes, and those classes are defined (and handled) in
> such a way that someone coming in via ssh ends up in a different
> user class than the same person coming in via telnet (or at a
> console login).
>
> Which OS is running on the machine being logged into? What is the
> output of 'ulimit -a' for an ssh connection vs a telnet connection
> (you should be able to 'telnet localhost' after ssh-ing into the
> host to find this out without leaving yourself open for packet-
> sniffers).
>
>
> ---
> Garance Alistair Drosehn = [EMAIL PROTECTED]
> Senior Systems Programmer or [EMAIL PROTECTED]
> Rensselaer Polytechnic Institute
>
