Hi All,

Did anyone use this command to kill the bshell processes?

bshcmd6.2
Usage: bshcmd6.2 [options] <bshell_pid>

-v : Print version
-p : Show process list
-m : Show memory usage
-d <dbglvl> : Set DEBUG_LEVEL to (octal) <dbglvl>
-k <pid> : Kill bshell process id <pid>
-e : Kill all bshell processes

I tried to use it, it didnt work. I have created a unix shell script which can kill a particular user or all the users for a particular bshell BUT it has to be executed only as the ROOT on Unix Box.

Any idea???

Thanks!

Hi,

U can use this command as follows

bshcmd6.2 -k <pid> <bshell_pid>

Regards.

USAGE:

-w <sec> : Wait <sec> seconds for bshell to execute command
-u <sec> : Send SIGUSR1 to bshell (wakeup). Only to be used in
combination with -w option. Waits <sec> seconds to
see if the command is executed.
-s : Show entire contents of logfile (if accessable)

For example :

bshcmd6.1 -s -u5 -w5 -p 32300

Shows all bshell processes of the bshell with PID=32300.
It is necessary to use options -w and -u, to "wake" the bshell.

bshcmd6.1 -e 32300
This command kills all bshell processes of the bshell with PID=32300.

The bshell PID can be seen using:
licmon6.1 -w
ps -aef |grep bshell

I hope this information is helpful. It is for BaanIVc4, but it should work in the same way for you (I hope ) if you replace 6.1 with 6.2.

Regards,

In my opinion it is best to have root to kill bshell processes as root should be restricted and thus also the killing of bshells. I am pretty sure most system admins are using a custom built script to do that job.

Hi All,

thanks for all your suggestions.

To give you the complete picture of the situation -

1. I have my own shell script which can kill all the users, based on a bshell... BUT I need to be a root to kill all users or use the setuid bit for that shell script.

2. we are working on the version-6.2 the latest baan release. I tried the bshcmd6.2 and it does kill the bshells. The new BaaN BW is using the Worktop than the old static browser. I had few sessions opened and I used the bshcmd6.2 to kill my bshell and I was expecting all the baan windows to close and logge out. Instead they were just present, while I noticed that the .bwc file from the startup was closed. So I guess the bshells are closed, when I click or close on of the baan windows all the baan windows are closed. But the main menu or the work top document remains open, which gives us a feeling that we are still connected/online and our bshell is not killed. When I click any session from my menu, then the worktop shows a status message, reconnecting and gets back online.

Since we are working on a new release I guess most of you might not be aware of these features.

3. We had an alternative idea so make a wrapper around the shell script that it executes as a root, more security for our unix admin guys and we can modify the script ourselves, than if the script is owned by the root.

any more ideas to share are welcome!