pwinter
6th October 2003, 15:49
Hi all,
I have developed a shell-script to monitor license usage. (didn't use "Closeidle" as I need to control things at server level). Also, due to our old porting set, had limited options!
The script does the following:
1. Take snap-shot of all bshell processes
2. Remove any obsolete bshell.<PID> files
3. use bshcmd6.1 to identify BaaN objects being run by each user in turn
4. append to a file any "idle" logins (which compare to various templates I have created)
5. Kill -15 sleeping bshells from the aforementioned file (should the number of users reach a defined number)
------------------------------------
My problem.....
The output of bshcmd6.1 appends to a RUNNING bshell.<PID> file. Because I am looping the process to a master list, these files grow quite quickly. The Job Daemon bshell file gets VERY big.
I don't really want to stop/start the job-schedule if I can avoid it.
Is there a way of reducing the size of a running bshell file? (I have tried "> /{BSE}/tmp/bshell.<PID>" to a test login file, only to find that it is re-created by the logic server at the next poll.

Sorry if this is a bit boring but the script is really useful to me.

Hope someone can help.

vahdani
6th October 2003, 23:51
Hi,

If you post your script, then there maybe someone who can help you. I personally hear about "bshell.<PID>" files for the first time. Many a funny critter seem to lurk in $BSE/tmp. :D

pemcgriff
18th October 2007, 18:23
Is there a way to capture the message that the user gets when there are no more licenses available and send an email to a helpdesk?

THis would give information on when and how frequent this is happening without having to run some batch process.

victor_cleto
19th October 2007, 11:53
On UNIX, why not put a monitoring script of the licenses (that could also do some cleaning up of unused ones) and that warns the helpdesk when the available ones reach zero?

simona
20th May 2008, 13:32
Hello :)

my bshell.4272 file growed up to 35 GB and still growing...
How this file came out?? How can I control it?? And can I avoid to "eat" my space and let me without license??

Thank you very much!

Simona from Romania



Hi all,
I have developed a shell-script to monitor license usage. (didn't use "Closeidle" as I need to control things at server level). Also, due to our old porting set, had limited options!
The script does the following:
1. Take snap-shot of all bshell processes
2. Remove any obsolete bshell.<PID> files
3. use bshcmd6.1 to identify BaaN objects being run by each user in turn
4. append to a file any "idle" logins (which compare to various templates I have created)
5. Kill -15 sleeping bshells from the aforementioned file (should the number of users reach a defined number)
------------------------------------
My problem.....
The output of bshcmd6.1 appends to a RUNNING bshell.<PID> file. Because I am looping the process to a master list, these files grow quite quickly. The Job Daemon bshell file gets VERY big.
I don't really want to stop/start the job-schedule if I can avoid it.
Is there a way of reducing the size of a running bshell file? (I have tried "> /{BSE}/tmp/bshell.<PID>" to a test login file, only to find that it is re-created by the logic server at the next poll.

Sorry if this is a bit boring but the script is really useful to me.

Hope someone can help.