Applicable versions and levels
Linux versions: 5.2, V10.0L10 or later
Action
Cause
In Linux versions, through processing called PAM authentication that is performed when the user logs in, the value set in /etc/security/limits.conf is reflected.
The operating system default value settings apply immediately after the operating system starts, and the operating system default value settings are also inherited by the Systemwalker Operation Manager daemon that is started in line with the operating system startup. In this state, the /etc/security/limits.conf value will not be reflected in the Systemwalker Operation Manager job.
Note that, in this state, if a user for whom the "ulimit" internal command of the shell is specified in the profile, such as .profile or .login, of the login shell, the following message may be output as the execution result of the job:
/etc/profile: line xxx: ulimit: open files: cannot modify limit: Operation not permitted. |
Note: xxx shows the line number of /etc/profile.
Action method
Take action using one of the following methods:
To enable the /etc/security/limits.conf value for a user application that is executed as a job, use one of the following methods to execute the job:
Specify "root" as the project owner, or in the Effective user name field in the Detail information tab of the Add/Change - Job window.
Register the following type of shell script content in the Command field in the Standard information tab of the Add/Change - Job window:
#!/bin/sh |
Note: <user name>: Specify the user that will execute the user application.
<script file name>: Specify the user application.When the effective user of all jobs is the administrator (root), after starting the operating system, log in to the Linux server and then restart the Systemwalker Operation Manager daemon to enable the /etc/security/limits.conf value.