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-
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
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
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
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
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
usage. Documented)
@USER.RETURN.CODE (This is actual usage. Documented)
@YEAR
Regards,
Dan
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of u2ug
Sent: Friday, June 18, 2010 8:29 AM
To: U2 Users List
Subject: Re: [U2
:53 PM
To: U2 Users List
Subject: Re: [U2] @LOGNAME... Changing @variables
I looked into this and there appears to be 2 different type of system
variables in UniData. There are those like @AM which cannot be changed
and those like @LOGNAME which can be. It is not required to pass them
I think @LOGNAME comes from windows which appears to cache it. We found
after changing the user names a reboot of the server was required to
bring in the updated name. We also have a .bat file which does an: ECHO
%USERNAME% but I don't recall which it returned.
For us the reboot was the easiest
Warning: This message has had one or more attachments removed
Warning: (not named).
Warning: Please read the AngelicHost-Attachment-Warning.txt attachment(s)
for more information.
Isn't @LOGNAME the group the user is a member of on Windows servers?
You may have had the users be in their own
10 matches
Mail list logo
