Ignite - UX : Unable to read error file "/var/tmp/eaaa21716" from remsh.

[Daniel Simard]

Hi,
I get the error when trying to network ignite a client. I was wondering if there's something that I'm doing wrong. I did play at one point with securing my /etc/services, /etc/inetd.conf and inetd.sec but the funny thing is that I've reverted back to the original files and this should work. I have also did a inetd -c in order for the files to be read.

Any suggestions ? Thanks!

[James R. Ferguson]

Hi:

There is nothing to worry about. This is a temporary file that *was* there when Ignite first probed, but was removed when Ignite went to copy it. The fact that it is in a temporary file directory ('/var/tmp/') leads to this deduction.

Regards!

...JRF...

[Steven E. Protter · Accepted solution]

As you tighten security, a something to think about.

Ignite uses the r- protoccols, remesh when you boot an Ignite client to begin a push install from the server.

So I leave those protocols in inetd.conf commented out so they can be uncommented followed by an inetd -c just prior to an Ignite push.

Comming from a highway here so I hope I understood your question.

SEP