I don't think so. My 1GB problem was when using a hamm system.
Commenting out ULIMIT in login.defs was the only way to raise the hard
limit on all accounts from what I could see.
On 27 Jan 1998, Kirk Hilliard wrote:
Steve Hsieh [EMAIL PROTECTED] writes:
To anyone interested in this --
To anyone interested in this --
The problem was not related to the kernel, but to ulimit.
/etc/login.defs has ULIMIT set to 1GB for some reason. However, it is
not clear to me why some accounts use this value, while other accounts
ignore it. In any case, if you comment out the ULIMIT line,
To anyone interested in this --
The problem was not related to the kernel, but to ulimit.
/etc/login.defs has ULIMIT set to 1GB for some reason. However, it is
not clear to me why some accounts use this value, while other accounts
ignore it.
Just guessing: do they use different
Steve Hsieh [EMAIL PROTECTED] writes:
To anyone interested in this --
The problem was not related to the kernel, but to ulimit.
/etc/login.defs has ULIMIT set to 1GB for some reason. However, it is
not clear to me why some accounts use this value, while other accounts
ignore it. In
On my machine running hamm:
$ ulimit
unlimited
I ran out of space at 1GB on the bo machine, but I don't have space to
check this on the hamm machine. Did anyone here run into a 1GB limit
on a hamm machine?
My hamm machine has a 1GB limit, that I don't remember ever
Ben Pfaff writes:
On my machine running hamm:
$ ulimit
unlimited
I ran out of space at 1GB on the bo machine, but I don't have space to
check this on the hamm machine. Did anyone here run into a 1GB limit
on a hamm machine?
My hamm machine has a 1GB limit, that I don't
Kirk Hilliard [EMAIL PROTECTED] writes:
ulimit = 1 GB
Aha! Then this might be fixed in hamm:
On my machine running bo:
$ ulimit
1048576
On my machine running hamm:
$ ulimit
unlimited
/etc/login.defs is part of the login package.
On my bo system its:
#ulimit
unlimited
I´m
7 matches
Mail list logo
