Skip to content

Problem with _LMFILES_000 in 3.1.0b #2

Closed

Description

@xdelaruelle

While experimenting a bit on John's case example, I noticed
a problem when the LMFILES string length was going to get
bigger than 960 characters; modules splits the variable into
two, _LMFILES_000 and _LMFILES_001. Once this happens, any
unload operation won't be reflected in these environment
variables.

Additionally, performing a switch operation results in a new
LMFILES variable being created, so modules only reports the
switched module as being loaded.

I can "cure" modules simply by fixing the environment vars.
Otherwise, continuing to attempt additional module commands
can result in a core dump.

This is occurring on a UltraSPARC 10 running SunOS 5.7
Generic_106541-07 with tcsh 6.07.02.

Any thoughts?

Reported by: rminsk

Activity

  1. self-assigned this
    on Sep 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions