-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 21 Jun 2000, Randolph J. Herber wrote:
> I suggest that you do not use rc.local. Rather, I suggest that you learn
> how to write and use your own script in /etc/rc.d/init.d (etc/init.d on
> some systems). Name that script so that sshd is started when you want
> it started in the sequence of start up events.
> I saw no mention of what your operating system or environment is; therefore,
> I can not offer any, more detailed suggestions.
> Randolph J. Herber, [EMAIL PROTECTED], +1 630 840 2966, CD/CDFTF PK-149F,
> Mail Stop 318, Fermilab, Kirk & Pine Rds., PO Box 500, Batavia, IL 60510-0500,
> USA. (Speaking for myself and not for US, US DOE, FNAL nor URA.) (Product,
> trade, or service marks herein belong to their respective owners.)
Gee, I would like to use vi to edit my files, would you show me how also?
Sir, you presumed too much.
;-)
Sheesh.
Whether I move when sshd is started in rc.local or put it in its own init.d
script, that is still a kludge. What if other problems happened before sshd
is started? and I get into the same situation?
I like the idea someone else suggested of putting another sshd in inetd at
a different port. I have such a setup on my home machine, but did not set
it up for this remote server. Sigh, Murphy's law.
Tin Le
- ----
http://tin.le.org
Internet Security and Firewall Consulting
Tin Le - [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2i
iQCVAgUBOVD41xiIIbPkDHhBAQEsLwP9ESpMgWQdQh83w6fJ6ZQoNmkDFrtYX4x2
r48WuDJ30oDlP7thxjfUlS8pcYALqUrXxvImdi6SedtxzhdHQ1zxBAdA6+OMxNeR
WeVZ6ZphI8S/D3Ssget4vueM78qpbk6cRnlBvNdhwpkneoBh6XXcyJYj9CKgWJdI
pRgfoIfwscM=
=QYC9
-----END PGP SIGNATURE-----
