Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #37

Closed
Open
Opened Sep 24, 2015 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

address cuserid() issue on BG/Q

The current BG/Q environment doesn't support cuserid(), which Darshan uses to identify the userid for each job. There is a ticket open with IBM to track this issue. If IBM doesn't address it, our fallback plan on BG/Q will be to use the $USER environment variable, and possibly hash it to generate a unique numerical id for each user.

Assignee
Assign to
better-perf-estimates
Milestone
better-perf-estimates
Assign milestone
Time tracking
None
Due date
None
2
Labels
defect wrapper libraries
Assign labels
  • View project labels
Reference: darshan/darshan#37