Date: Fri, 4 Jun 1999 09:25:08 -0700 (PDT) From: Roger Marquis <marquis@roble.com> To: security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) Message-ID: <Pine.GSO.3.96.990604090608.5931H-100000@roble2.roble.com> In-Reply-To: <199906041540.IAA21218@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> What does a typical path variable look like on your systems??? Long > paths are bad for shells. Yea, I know, the hashing stuff should keep > a single copy of a shell pretty quick, but every time you fork off > another one your going to have to go hash the path list. For applications like ssh, with less than a couple dozen files total, we don't even bother to create subdirectories for sbin, bin, etc. The "configure" command line typically looks like: ./configure --prefix=/var/ssh --bindir=/var/ssh \ --exec-prefix=/var/ssh --sbindir=/var/ssh --sysconfdir=/var/ssh \ --with-etcdir=/var/ssh --without-rsh It would be nice if these variables could be set globally i.e., %grep PREFIX /usr/ports/Makefile PREFIX= prompt_for #PREFIX= %grep ETCDIR /usr/ports/Makefile ETCDIR= $PREFIX/etc #ETCDIR= /usr/local/etc ... Our particular setup installs under /var since /usr/local is an NFS mount. Ssh, scp and sftp are kept in user's paths with symlinks i.e.: ln -s /var/ssh/ssh /usr/local/bin/ssh ln -s /var/ssh/scp /usr/local/bin/scp ln -s /var/ssh/ssh-keygen /usr/local/bin/ssh-keygen This allows us to maintain a uniform /usr/local while accommodating local differences. It scales nicely up to several hundred hosts and reduces sysadmin overhead by orders of magnitude. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.990604090608.5931H-100000>