Conference irnbru::ims_api

	
	Can I please make a few requests for the next release of
	the Master on Digital UNIX ?

	firstly,

	When the user types "masterc start" an .intmp file is created
	which contains a line of the form:

		<INPUT FILE>   >   <OUTPUT FILE>

	Can this please be change to:

		<INPUT FILE>   >&   <OUTPUT FILE>

	so that stderr is also directed to the OUT FILE.



	2ndly, when users try to stop servers, errors like

		-166

	meaning the server isn't running, OR

		<some success stmt followed by>
		CLIENT NOT AUTHORISED

	meaning there is no

		..../<server>_organic.sec 

	file in existance.

	
	Speaking of security files, is it 

		<node>::<user> 

	OR
	
		<user>::<node>

	??


	I assume either can be "*" so it means

		"User X is permitted from Any node"

	in the case where the <node> part is an asteris, 

	OR,

		"Any user on node N is permitted"

	in case where the <user> part is an asteris.



	Also, we notice the master_server writes to the screen
	for errors such as the <INPUT> file is not executable
	when a START is attempted.

	Sorry for being a bit pedantic 
	
	Thanks,

	Craig.

>>	When the user types "masterc start" an .intmp file is created
>>	which contains a line of the form:
		<INPUT FILE>   >   <OUTPUT FILE>
>>	Can this please be change to:
>>		<INPUT FILE>   >&   <OUTPUT FILE>
>>	so that stderr is also directed to the OUT FILE.

We shall provide an option for this. The default behaviour will not change.

>>	2ndly, when users try to stop servers, errors like
>>		-166
>>	meaning the server isn't running, OR
>>		<some success stmt followed by>
>>		CLIENT NOT AUTHORISED
>>	meaning there is no
>>		..../<server>_organic.sec 
>>	file in existance.

If you are saying these aren't meaningful enough then we agree. We're hoping
to be able to overhaul these in the next major release.
	
>>	Speaking of security files, is it 
>>		<node>::<user> 

Yes

>>	OR
>>		<user>::<node>

No

>>	I assume either can be "*" so it means
>>		"User X is permitted from Any node"
>>	in the case where the <node> part is an asteris, 

Yes

>>      OR
>>		"Any user on node N is permitted"
>>	in case where the <user> part is an asteris.

Still Yes
Basically the * is a wildcard that can be used on either side. So

	*::SYSTEM

means any system account on any machine and

	IRNBRU::*

means any user on node IRNBRU.

>>	Also, we notice the master_server writes to the screen
>>	for errors such as the <INPUT> file is not executable
>>	when a START is attempted.

That is intended.

>>	Sorry for being a bit pedantic 
	
Suggestions for improvements are always welcome.

Cheers,
Dave M.