I don't know for sure, but my best guess is that you need to look at using a profile to set ENV to include an appropriate TMPDIR (if necessary) as well as to kick off the ssh-agent process.
>From the man page for rksh/ksh: *-r* Restricted shell. A shell is ârestrictedâ if this option is used; if the basename the shell was invoked with was ârkshâ; or if the SHELL parameter is set to ârkshâ. The following restrictions come into effect after the shell processes any profile and ENV files: - The *cd* command is disabled. - The SHELL, ENV, and PATH parameters cannot be changed. - Command names can't be specified with absolute or relative paths. - The *-p* option of the built-in command *command* can't be used. - Redirections that create files can't be used (i.e. â>â, â>|â, â>>â, â<> â). And from the man page for ssh-agent: FILES *$TMPDIR/ssh-XXXXXXXXXX/agent.<ppid>* UNIX-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The sockets should get automatically removed when the agent exits. Hope this helped.
