[U2] @LOGNAME on Unidata
We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on RedHat. We make use of @LOGNAME quite a bit to determine a person's username. Since our migration, however, we've documented some cases where @LOGNAME is not returning the proper username - it returns someone else's. What's bizarre is that most of the time it's right, but occasionally it's not. Has anyone seen or heard of this? When we had a report of this (with documentation) I thought it was weird. Today we just got a call about a different problem which I'm 99% sure is tied to this since it makes use of @LOGNAME. Like the above, sometimes it's correct, sometime it's wrong. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
I have seen this in the past where the file wtmp usually found in /var/adm is corrupt or too big ( over 2 meg ). To correct this just type at the unix prompt wtmp And it will clear the file.I recommend doing this just before a reboot of the system. -Dan -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera Sent: Thursday, June 17, 2010 2:04 PM To: U2 Users List Subject: [U2] @LOGNAME on Unidata We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on RedHat. We make use of @LOGNAME quite a bit to determine a person's username. Since our migration, however, we've documented some cases where @LOGNAME is not returning the proper username - it returns someone else's. What's bizarre is that most of the time it's right, but occasionally it's not. Has anyone seen or heard of this? When we had a report of this (with documentation) I thought it was weird. Today we just got a call about a different problem which I'm 99% sure is tied to this since it makes use of @LOGNAME. Like the above, sometimes it's correct, sometime it's wrong. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
On 06/17/10 14:20, Dan Goble wrote: I have seen this in the past where the file wtmp usually found in /var/adm is corrupt or too big ( over 2 meg ). To correct this just type at the unix prompt wtmp And it will clear the file.I recommend doing this just before a reboot of the system. Thanks Dan. Our wtmp is under 1Meg and just rotated this week, so I can't imagine this is the culprit, but I'll give it a whirl... -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
On 6/17/2010 2:23 PM, Jeffrey Butera wrote: On 06/17/10 14:20, Dan Goble wrote: I have seen this in the past where the file wtmp usually found in /var/adm is corrupt or too big ( over 2 meg ). To correct this just type at the unix prompt wtmp And it will clear the file.I recommend doing this just before a reboot of the system. Thanks Dan. Our wtmp is under 1Meg and just rotated this week, so I can't imagine this is the culprit, but I'll give it a whirl... We had an issue similar to this, but I am having difficulty recalling what the issue was. It was the strangest thing, right much of the time, but consistently it would not be correct. Some things that come to mind, named (or un-named) COMMON. Re-entrant programs. I will check with some team members. It has been probably 5-10 years since this issue for us. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
On Universe you can use SYSTEM(19) instead of @LOGNAME. It might exist on Unidata too. I don't know if @LOGNAME gets it from the Unix environment LOGNAME variable. If so, there may be a Unix script that is changing the environment variable. You can try: - Original Message From: Jeffrey Butera jbut...@hampshire.edu To: U2 Users List u2-users@listserver.u2ug.org Sent: Thu, June 17, 2010 2:04:08 PM Subject: [U2] @LOGNAME on Unidata We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on RedHat. We make use of @LOGNAME quite a bit to determine a person's username. Since our migration, however, we've documented some cases where @LOGNAME is not returning the proper username - it returns someone else's.What's bizarre is that most of the time it's right, but occasionally it's not. Has anyone seen or heard of this? When we had a report of this (with documentation) I thought it was weird. Today we just got a call about a different problem which I'm 99% sure is tied to this since it makes use of @LOGNAME. Like the above, sometimes it's correct, sometime it's wrong. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
Hi Jeff, While at Beloit I had a problem with @LOGNAME. It only showed up when a Datatel program was calling another Datatel program (or something like that). I know it had something to do with a problem with Uniobjects and PAM authentication. The work-around was to add the DMI username and password in a DMIEXTS record. We used a Datatel subroutine to control access to budgets for reports such as the trial balance report. Turned out the report thought everyone was datatel. Worse yet, at the time we found this out, the user datatel was setup to have wide open budget access. I'm wondering if Datatel's strange world of listeners is involved in your case. On the other hand; going to Unidata 7.2.x was the solution for our budget access problem as I was able to undo the above work-around. --- On Thu, 6/17/10, Jeffrey Butera jbut...@hampshire.edu wrote: From: Jeffrey Butera jbut...@hampshire.edu Subject: [U2] @LOGNAME on Unidata To: U2 Users List u2-users@listserver.u2ug.org Date: Thursday, June 17, 2010, 2:04 PM We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on RedHat. We make use of @LOGNAME quite a bit to determine a person's username. Since our migration, however, we've documented some cases where @LOGNAME is not returning the proper username - it returns someone else's. What's bizarre is that most of the time it's right, but occasionally it's not. Has anyone seen or heard of this? When we had a report of this (with documentation) I thought it was weird. Today we just got a call about a different problem which I'm 99% sure is tied to this since it makes use of @LOGNAME. Like the above, sometimes it's correct, sometime it's wrong. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting begin_of_the_skype_highlighting 413-559-5556 end_of_the_skype_highlighting ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] @LOGNAME on Unidata
We ran into a similar situation in the past with uv on hpux Although @LOGNAME is documented as a readonly value, we found out that it is possible to change it ( and other readonly system variables ) by passing it as an argument to a subroutine - the subroutine can then change the value. I guess uv doesn't actually mark the variable as readonly in any way at run time - readonliness is a compile time attribute - so a subroutine has no idea that its calling args are readonly system variables - so in effect they aren't. Look for any subroutines called with @LOGNAME as an argument then check that the sub doesn't alter that argument. Given : ... CALL *SOMESUB( @LOGNAME ) ... DEFINE SUBROUTINE SOMESUB ( ARG ) ... * this will change the argument value in the calling routine * including 'readonly' system variables ARG=Something ... END Pass temp variable instead of @LOGNAME : CALL *SOMESUB( @LOGNAME: ) -or- CALL *SOMESUB( (@LOGNAME) ) -or- Ensure that argument is never modified in the routine -- DEFINE SUBROUTINE SOMESUB ( ARG.IN ) ARG=ARG.IN ;* the only place IARG is ever used ... ARG=SomethingElse ... END Note that this also applies to functions and routines called via SUBR() and once the variable is changed it is changed for the lifetime of the current session not just for the current program. Gerry -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera Sent: June 17, 2010 02:04 PM To: U2 Users List Subject: [U2] @LOGNAME on Unidata We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on RedHat. We make use of @LOGNAME quite a bit to determine a person's username. Since our migration, however, we've documented some cases where @LOGNAME is not returning the proper username - it returns someone else's. What's bizarre is that most of the time it's right, but occasionally it's not. Has anyone seen or heard of this? When we had a report of this (with documentation) I thought it was weird. Today we just got a call about a different problem which I'm 99% sure is tied to this since it makes use of @LOGNAME. Like the above, sometimes it's correct, sometime it's wrong. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
