-
- Downloads
This patch contains more safe checking in syscall rlimit and unit tests
The soft limit is the value that the kernel enforces for the corresponding resource
The hard limit acts as a ceiling for the soft limit
an unprivileged process may only set its soft limit to a value
in the range from 0 up to the hard limit.
So in order to make the change in fds count without any error we should
inform the user to make the process have CAP_SYS_RESOURCE capability
in order to set the hard limit.
License: MIT
Signed-off-by:
hoenirvili <hoenirvili@gmail.com>
Showing
- cmd/ipfs/daemon.go 3 additions, 5 deletionscmd/ipfs/daemon.go
- cmd/ipfs/ulimit.go 0 additions, 19 deletionscmd/ipfs/ulimit.go
- cmd/ipfs/ulimit_freebsd.go 0 additions, 45 deletionscmd/ipfs/ulimit_freebsd.go
- cmd/ipfs/ulimit_unix.go 0 additions, 43 deletionscmd/ipfs/ulimit_unix.go
- cmd/ipfs/util/ulimit.go 91 additions, 0 deletionscmd/ipfs/util/ulimit.go
- cmd/ipfs/util/ulimit_freebsd.go 27 additions, 0 deletionscmd/ipfs/util/ulimit_freebsd.go
- cmd/ipfs/util/ulimit_test.go 88 additions, 0 deletionscmd/ipfs/util/ulimit_test.go
- cmd/ipfs/util/ulimit_unix.go 27 additions, 0 deletionscmd/ipfs/util/ulimit_unix.go
- cmd/ipfs/util/ulimit_windows.go 7 additions, 0 deletionscmd/ipfs/util/ulimit_windows.go
Loading
Please register or sign in to comment