Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
73f89adf
Commit
73f89adf
authored
11 years ago
by
David Bigagli
Browse files
Options
Downloads
Plain Diff
Merge pull request #68 from jwm/bug-559-comment-sync
sync comment with new PW_BUF_SIZE
parents
157e1f46
22147ba4
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/common/uid.h
+1
-1
1 addition, 1 deletion
src/common/uid.h
with
1 addition
and
1 deletion
src/common/uid.h
+
1
−
1
View file @
73f89adf
...
@@ -48,7 +48,7 @@
...
@@ -48,7 +48,7 @@
* In an ideal world, we could use sysconf(_SC_GETPW_R_SIZE_MAX) to get the
* In an ideal world, we could use sysconf(_SC_GETPW_R_SIZE_MAX) to get the
* maximum buffer size neede for getpwnam_r(), but if there is no maximum
* maximum buffer size neede for getpwnam_r(), but if there is no maximum
* value configured, the value returned is 1024, which can too small.
* value configured, the value returned is 1024, which can too small.
* Diito for _SC_GETGR_R_SIZE_MAX.
Use 64k byte buffer by default.
* Diito for _SC_GETGR_R_SIZE_MAX.
*/
*/
#define PW_BUF_SIZE 524288
#define PW_BUF_SIZE 524288
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment