>>> sender: "Radu Oprisan" date: "Fri, Feb 09, 2007 at 01:03:38AM +0200" <<<EOQ
> Teodor Cimpoesu wrote:
> >On 2/8/07, Radu Oprisan <[EMAIL PROTECTED]> wrote:
> >>Teodor Cimpoesu wrote:
> >>>
> >>> iacata ca "Ma indoiesc ca in bash poti sa faci asa ceva." se poate :-P
> >>
> >>Corect... dar chestia asta, scalata la mai mult de 20 de fork-uri o sa
> >>iti duca procesoru' in lumea ailalta :) nu ca perl-u ar fi mai smecher
> >>
> >[divaghez palind un pic spre OT de dragul artei...]
> >
> >hm, nu vad unde ar fi problema si la 100 de fork-uri, numai sa nu
> >ajungi la limita de procese per utilizator
>
> Limita de procese per utilizator???? Nu mai zi nimic daca tot vorbesti
> ca sa te afli in treaba. In cel mai rau caz, nu poti sa spawnezi mai
> multe fork-uri decat nr maxim de pid-uri, care ultima data parca era
> unsigned int.
$ man ulimit
ulimit [-SHacdflmnpstuv [limit]]
Provides control over the resources available to the shell and to
processes started by it, on systems that allow such control. [..]
-a All current limits are reported
-c The maximum size of core files created
-d The maximum size of a process’s data segment
-f The maximum size of files created by the shell
-l The maximum size that may be locked into memory
-m The maximum resident set size
-n The maximum number of open file descriptors (most systems
do not allow this value to be set)
-p The pipe size in 512-byte blocks (this may not be set)
-s The maximum stack size
-t The maximum amount of cpu time in seconds
-u The maximum number of processes available to a single user
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-v The maximum amount of virtual memory available to the shell
Se pare ca nu vorbea ca sa se afle in treaba... ;-) si se mai pare ca nu sta
toata ziua ca root :-)) damn, ar trebui sa incerc si eu uneori...
Numai bine,
Alex
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
