* Matthew H. Ray ([EMAIL PROTECTED]) spake thusly: > I have a small cluster of Woody machines (fresh install) and I've run > into problems running apt-get with SSH. While trying to install > packages on all the machines with dsh, I started getting apt-get > problems, so I tried it with just ssh on the individual machines. It > appears that SSH is losing it's knowledge of the PATH while executing. > I used ssh-keygen so I wouldn't have to do logins (thus no password > request). > > [EMAIL PROTECTED] # ssh larry "echo $PATH; apt-get install rdate" > /sbin:/bin:/usr/sbin:/usr/bin:/usr/bin/X11:/usr/local/sbin:/usr/local/bin > Reading Package Lists... > Building Dependency Tree... > The following NEW packages will be installed: > rdate > 0 packages upgraded, 1 newly installed, 0 to remove and 0 not > upgraded. > Need to get 0B/7040B of archives. After unpacking 65.5kB will be used. > dpkg: `ldconfig' not found on PATH. > dpkg: `start-stop-daemon' not found on PATH. > dpkg: `install-info' not found on PATH. > dpkg: `update-rc.d' not found on PATH. > dpkg: 4 expected program(s) not found on PATH. > NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and > /sbin. > E: Sub-process /usr/bin/dpkg returned an error code (2) > > and if I log onto larry > > [EMAIL PROTECTED] # which ldconfig start-stop-daemon install-info update-rc.d > /sbin/ldconfig > /sbin/start-stop-daemon > /usr/sbin/install-info > /usr/sbin/update-rc.d > > Is this a bug in ssh or dpkg?
Try adding "PATH=/bin:/sbin:/usr/bin:/usr/sbin" to /root/.ssh/environment. Dima -- One distinguishing characteristic of BOFHen is attention deficit disorder. Put me in front of something boring and I can find a near-infinite number of really creative ways to bugger off. -- ADB
