Hi, all.

I changed daemon from rexec to blogind.
In case of rexec, i could get access log by looking syslog but,
blogind, i don't know how i can get access log.

i found log.blogind file in $BSE/log but it's seems just for daemon, not for user access.

Please advice for me:(

Thanks

Independent from blogin or recex you can see, I think, all you need in two locations:

a) $BSE/log/licd6.1 shows an entry, whenever a bshell registers itself with the licence daemon. This is obviously usually at login time

b) $BSE/lib/TIME.HIS logs for a user, the start end end date/time of each session, if you enable history in the user properties. This creates only a minor performance overhead, as this is only written, when a user ends a session of menu.

The blogind also has an option "-v", maybe this is standing for "verbose" and writes more entries to the log. But I did not try this.

Regards

Markus

Minor correction to Markus's reply:
The blogind also has an option "-v", maybe this is standing for "verbose" and writes more entries to the log. But I did not try this.

>blogind6.2 -U
blogind6.2: Unknown argument: -U
Usage: blogind6.2 [-vV] [-d] [-fg] [-p Portnumber] [-kK] [-info] [-home ProgramH
ome]
-k : kill running blogind6.2 (if running as background process)
-fg : run blogind6.2 as foreground process (for debug purposes only)
-p : override default TCP/IP listening port
-d : debug info for daemon 'blogind6.2'
-info : tells which protocols are available for daemon 'blogind6.2'
-home : set program home directory for ASM only. Mandatory argument for ASM!
-v : displays version information
ayamylv, check for Markus' response, else please state your requirement/issue clearly.

Thanks Markus, NPrao.

I checked log.licd6.1.
There were some informations what I need.

I tried "blogind6.1 -v", as NPRao said, many informations about OS, Platform, etc. appered. Those were things what in blogind6.1(I watched that using "strings" command).

Other hand, I tried to add access log to syslog using inetd.
But I couldn't that.
I edited /etc/inetd.conf & /etc/services.
Actuary, Inetd seems running, because BaanLogin port has been opened.
But BWC said an error message like "Block couldn' t be read"(Sorry I missed capture).
I think , it's because of blogind uses BaanLogin protocol(rexec uses tcp).

So, What are defferences between tcp and BaanLogin Protocol?

Thank you & Best Regards.

I think you are looking for a Unix solution for something, which is allready solved in Baan:

a) blogind is a real daemon by itself, which listens on a socket. It is not like telnetd, which basically waits to be started by inetd to get a stream passed.

b) The successfull logins can be seen in log.licd6.1, the failed in log.blogind and the started sessions in TIME.his.

So what are you actually looking for?

Thank you for great informations, Markus.

Sorry, I didn't say what I'm looking for clearly.

I am looking for access informations such as "Who", "When", "From Where", "How(rexec/blogind)" and "Result(Successful/Failed)" about baan.
And if possible, I want to add them to syslog.

All of my users usually used rexec to access to baan.
So, I could always get access logs from syslog.
But a part of users said to me that they wanted to use BaanLogin.
I started blogind6.1 and edited syslog.conf(inserted "daemon.info /var/adm/syslog/syslog.log) for getting logs on syslog.
But, They didn't appear on there.

So First, I was looking for access log files for baan because I didn't know log.licd6.1 & TIME.HIS.
By your aid, I knew them.
I could get two things "Who" and "When".
And log.blogind told me "Failed".

Next, I was looking for the way to add them on syslog.
But, I'm sorry. It ' suitable for here. It's an Unix solution as you said.

Now, I'm looking for informations about "From where" and "How"
Do you know that?


Thank you and Best Regards.

Hi ayamylv,

one reason why you as a unix person might also appreciate blogind should be that the password is passed encrypted, why with rexecd it is passed in the open.

Now to your question "from where":

I think this is actually not so easy but can be done. Some of my customers wanted to actually find out the where, so that they can restrict double logins from the same PC, but still allowing double logins with the same user name.

So the solution we are using there is to use a little utility called "lsof" and some scripting to get the TCP source adress of the bshell. This works pretty well. The trick is to configure baan not to call directly the bshell, but a script, when the GUI connects to baan. This is done by changing a file called ipc_info in $BSE/lib. Search the board for ipc_info and you should find plenty of hits how to do this.

Regards

Markus

Hi Markus.

I searched lsof...It's good tool.
I'll ask to my Boss if I can install lsof to our server.

Thank you and Best Regards.