remote enable creates txt file in pwd, which causes problems in a multi-user environment

[kmpeters]

The remote enable option of the softioc/xxx.pl script creates the txt file with the procServ info in the PWD, which is often the user's home directory:

xxx/iocBoot/iocxxx/softioc/commands/remote.pm

Line 34 in 01af9a4

system("cd $FindBin::RealBin; $PROCSERV --allow --quiet --oneshot -L $LOG_FILE -i ^C --logoutcmd=^D -I $prefix.txt $ip_addr:$port $FindBin::RealBin/$FindBin::RealScript remote commandline");

This causes problems when trying to start an IOC as different user account, which lacks the info file in its home directory, resulting in the IOC being started in screen session by the 2nd user account, rather than the procServ session of the 1st user account.

[kmpeters]

One possible fix it to put the .txt file somewhere in the IOC's directory.

[kmpeters]

@keenanlang, which directory is $FindBin::RealBin?

[keenanlang]

$FindBin::RealBin is the full path of the directory the xxx.pl script is in, regardless of where it is symlinked to or where it is being called from

[keenanlang]

I believe that 461c60d was added in order to make sure the file is created within the softioc directory, instead of the present directory

[kmpeters]

19ID is using the latest version of the scripts that have the change in 461c60d.

The problem may come from the fact that I had to hard-code many of the env vars because the IOC's binary and startup dir don't reside in the same top-level directory as the softioc scripts:

	$ENV{TOP} = "/net/s19iddserv/xorApps/epics/synApps_6_3/ioc/19idXSP3";
	$ENV{IOC_NAME}="XSP3_7Chan";
	$ENV{IOC_BINARY}="xspress3App";
	$ENV{IOC_BIN_DIR}="/home/xspress3/epics/xspress3/iocs/xspress3IOC/bin";
	$ENV{IOC_STARTUP_FILE}="st.cmd";
	$ENV{IOC_STARTUP_DIR}="/home/xspress3/epics/xspress3/iocs/xspress3IOC/iocBoot/ioc_7Channel";
	$ENV{IOC_COMMAND_DIR}="/net/s19iddserv/xorApps/epics/synApps_6_3/ioc/19idXSP3/iocBoot/ioc19idXSP3/softioc/commands";

I'll have to do more testing during the next shutdown.