I dealt with a similar problem by way of using the pam-regex[1] module to simply transform all entered usernames to lower case... as long as your user names (on the Linux side) are all *supposed* to be lower case, that should do the trick :)
(Had the bonus of also solving all sorts of other problem, e.g. things like file access, if people randomly capitalized their user names.) Tina [1] http://puszcza.gnu.org.ua/software/pam-modules/manual/html_chapter/ regex.html On Thursday, 12 April 2018 16:40:03 BST berg...@merctech.com wrote: > We're using SoGE 8.1.6 in an environment where users may login to the > cluster from a Linux workstation (typically using a lower-case login > name) or a Windows desktop, where their login name (as supplied by the > enterprise Active Directory) is usually mixed-case. > > On the cluster, we've created two passwd entries per-user with an > identical UID, so there's no distinction in file ownership or any > permissions or access rights at the Linux shell level. Most users don't > notice (or care) about the case that's shown when they login. > > However, SoGE seems to use the login name literally, not the UID. > > This causes two problems: > > job management > User "smithj" cannot manage (qdel, qalter) jobs > that they submitted as "SmithJ" > > > scheduler weighting > Using fair-share scheduling, John Smith will get > a disproportinate share of resources if he submits > jobs as both "smithj" and "SmithJ" vs. Jane Doe > who only submits jobs from her Linux machine as > "doej". > > Is there a way to configure SoGE to treat login IDs with a > case-insensitive match, or to use UIDs? > > We use a JSV pretty extensively, but I didn't see a way to alter login > names via a JSV -- any suggestions? > > Thanks, > > Mark > > > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
