arul@sdsu.UUCP (Arul Ananthanarayanan) (04/22/89)
I seem to have run into some difficulty in trying to set up anonymous ftp on a local 3b2/310 SYSV release 3.1, with WIN/TCP2.1 Specifically the "ls" command does not work. I can log in and cd and use get and put to receive files, but I can't see anything. This is the only machine that I have run into problems with during the use of anonymous ftp. Following the manual for ftpd I got anonymous ftp to work on our BSD machines and several Motorola SYSV boxes so this problem seems to be specific to the 3b2. Any help would be appreciated. Thanks, Arul -- San Diego State University Math Sciences Dept. Celerity 1230 BSD 4.3 UUCP: ....!ucsd!sdsu!arul work:(619) 594-7207 ARPA: arul%sdsu.uucp@ucsd.edu home:(619) 583-0439
stevea@laidbak.UUCP (Steve Alexander) (04/24/89)
In article <3745@sdsu.UUCP> arul@sdsu.UUCP (Arul Ananthanarayanan) writes: >I seem to have run into some difficulty in trying to set up >anonymous ftp on a local 3b2/310 SYSV release 3.1, with WIN/TCP2.1 >Specifically the "ls" command does not work. I can log in and cd and >use get and put to receive files, but I can't see anything. It sounds like your ls was linked with the shared C library (-lc_s). In ~ftp, make a directory called ``shlib'' and copy /shlib/libc_s to ~ftp/shlib. That should fix the problem. Ftpd does a chroot(2) system call when the anonymous user logs in, in order to provide protection for files on the system. After the chroot, /shlib is not accessible for ~ftp/bin/ls, so the ftp area needs to have its own copy. Alternatively, if you have source, you can recompile ls and link it with the non-shared library and avoid all of this hassle. -- Steve Alexander, TCP/IP Development | stevea%laidbak@sun.com Lachman Associates, Inc. | ...!sun!laidbak!stevea
scott@rdahp.UUCP (Scott Hammond) (04/28/89)
In article <2264@laidbak.UUCP> stevea@laidbak.UUCP (Steve Alexander) writes: >In article <3745@sdsu.UUCP> arul@sdsu.UUCP (Arul Ananthanarayanan) writes: >>[/bin/ls doesn't work for anon ftp on 3b2/310, SYSV 3.1, WIN3b/2.1] >It sounds like your ls was linked with the shared C library (-lc_s). >In ~ftp, make a directory called ``shlib'' and copy /shlib/libc_s to >~ftp/shlib. That should fix the problem. That is very interesting. The AT&T hotline response to an identical question though involving WIN3b/1.1 was to upgrade to a newer WIN/3b. At the time, upgrading was not an option. My solution was to use a SYSV 2.1.2 /bin/ls binary from a 3b15 (my approach was trial&error "what's wrong with ftp and ls and what can I try"), never thinking that I was having shared library problems. Now I know why this worked. -- Scott Hammond, R & D Associates, Marina del Rey, CA (213) 822-1715 : {ksuvax1,zardoz}!rdahp!scott : scott@harris.cis.ksu.edu