How can I log Baan GUI users? (like "last")

(UNIX, Baan IVc, Baan GUI, bw)

Is there any possibility to find out the last login of a Baan GUI user?
The UNIX command "last" doesn't do that for GUI users.

Yours
Markus

Hi,,

You can take a look into olg.licd6.1 and log.licd6.1.
(To look for login in the past, depends on how many users are able to login to Baan and how many times they do it, because in this file you can see the 'registered and unregistered login. Both files contains about 100 login or logoffs)

GN

Thanks, Djie-En

But this I tried already. But we have about 150 Users and lot of login/logout. So I can't see the history for more than one or two days.

Yours
Markus

If you turn on history for all users, you can also trace the activity of the users. Search for TIME.HIS and/ or history to see more topics on this subject.

Hope this helps,
Dick

Thanks, Dick.

I know this, but this is to much data.
In fact, I need just a similar command like "last", but for GUI users (which are not listed in "last").

Yours
Markus

I am not sure (I have no unix machine on hands) but I believe that during the login your .profile is still accessed. Can you check the last access time of your .profile?

Regards,
Han Brinkman

I would also use the TIME.HIS for this purpose, but if you find this too much data, then how about writing a small bshell wrapper, which logs all new bshell starts, something like:

echo $LOGNAME >> /tmp/last.log
exec $BSE/bin/bshell6.1 $*

Be aware that sometime the LOGNAME is not properly set, so you might have to take the output of the id command. This allways works!

Hi Markus,

Your idea is excelent! As I write wrappers for all kind of things (tracing, debugging etc) I should have come up with this by myself. But the honour is up to you. Maybe it can also be extended like:

echo "LOG ON " $LOGNAME " " `date`>> /tmp/last.log
exec $BSE/bin/bshell6.1 $*
echo "LOG ON " $LOGNAME " " `date`>> /tmp/last.log

As I don't have access to a system now, you have to test it by yourself. Any way, for all Unix versions this will work.

Kind regards,
Dick

You can also make a small 3-GL program and add it to BMS Mask Data (ttadv4188m000) which is executed whenever a user is logs in and it can write into a file or update into a small table. We have a similar tool, refer to -

Client Info (http://www.baanboard.com/baanboard/showthread.php?t=10001)

Markus's idea is good as long as you use single bshell entry in $BSE/lib/ipc_info. If you have multiple bshell tags like - bshell_admins, bshell_developers, bshell_endusers, bshell_jobs then all the different log.bshell's are then redirected to log.bshell6.2. And if you have many BaaN users on the system, the log files can get big enough and rolls over to olg files and makes it hard to find the errors.

Thanks, Markus and Dikkie.

I understand a little bit. But have I to put this lines into the .profile? Or how to start as a shell script?

Regards
Markus Wilhelm

Hi Dikkie,


your extension will not work like this exactly. The "exec" will overload the running process, this way a shell process is saved, but the last echo command will not be executed.

If you want to execute something behind the bshell call, then just remove the "exec".

For Markus Wilhelm:

You will find lots of topics in regards to "bshel wrappers" here on the forum. They are usefull for all sorts of things, like restricting access, setting environment variables, password aging etc.

The idea is to change the ipc_info file in $BSE/lib to execute a self written script instead of the origional bshell. This script performs some extra work (like logging users) and then calls the bshell.

Putting it in the profile will not work, as it is not executed by gui users.

regards

Markus

To see the last GUI login do :
ls -ultr $BSE/lib/user/u* , which gives the last read access of the file

Regards,

Frits Niesen

Hi - just thought I would let you guys know about the free client tool we have available that will tell you the following for each login:

Last time users logged in
Their User Name
Their OS Version
Their BW Client Version
Their PC Name
Their IP Address

Basically info needed for troubleshooting the client's. A script is running that captures this info, then there is a display session to view. We have versions for IV or V. These tools were passed out at the last BWU conference, and quite a few people are using them with success. You can download and try them out at:

Link to RMCis Client Tool (http://www.rmcis.com/tools.html)

I subscribe to the theory that one cannot have too many tools (and I have the garage to prove it).

I didn't realize at first that I was reading a thread that started 4 years ago. Some of us have come a long way since then. lol :)