We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original report (BitBucket issue) by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
On job resubmission, segway-wrapper.sh attempts to raise both the hard and soft limits of virtual and resident set size memory.
If the hard limit of memory is not unlimited, only root users may increase the hard memory limit requested even after it has been lowered.
Perhaps a proprosal to fallback to attempting to change only the soft limit after failing to set both hard and soft limit.
e.g:
#!bash ulimit -c 0 -v "$mem_limit_kb" -m "$mem_limit_kb" || ( ulimit -S -c 0 -v "$mem_limit_kb" -m "$mem_limit_kb" || exit 201)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Original report (BitBucket issue) by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
On job resubmission, segway-wrapper.sh attempts to raise both the hard and soft limits of virtual and resident set size memory.
If the hard limit of memory is not unlimited, only root users may increase the hard memory limit requested even after it has been lowered.
Perhaps a proprosal to fallback to attempting to change only the soft limit after failing to set both hard and soft limit.
e.g:
The text was updated successfully, but these errors were encountered: