1752777 Members
5979 Online
108789 Solutions
New Discussion юеВ

Re: warning secure ftp

 
Jose Ramirez_6
Advisor

warning secure ftp

Hi.

I have a problem When I execute the command dir inside FTP.

The warning that ftp reply is:

220 ceco FTP server (Version 1.1.214.4(PHNE_30990) Mon Nov 15 12:47:12 GMT 2004)
ready.
Usuario (192.185.1.248:(none)): elarbol
331 Password required for elarbol.
Contrase┬▒a:
230 User elarbol logged in. Access restrictions apply.
ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for /usr/bin/ls.

Warning! One or more of your selected locales are not available.
Please invoke the commands "locale" and "locale -a" to verify your
selections and the available locales.

Continuing processing using the "C" locale.

total 2
drwxrwxrwx 2 0 3 96 Dec 12 20:34 arbol
drwxrwxrwx 2 0 3 96 Dec 12 22:11 sdf
drwxrwxrwx 4 0 3 1024 Feb 28 2005 usr
226 Transfer complete.
ftp: 428 bytes recibidos en 0,00Segundos 428000,00KB/s.
ftp>


thank you for help me.
jose ramirez
5 REPLIES 5
Piergiacomo Perini
Trusted Contributor

Re: warning secure ftp

Hi Jose,
warning is about language in use by user that
perform ftp.

Some environment variable are involved like
LANG , LC_TIME, LC_NUMERIC
(see man locale for further infos).

Hope this help

regards
Jose Ramirez_6
Advisor

Re: warning secure ftp

Hi Perini:

I have verified the value of thist variable whit the command LOCALE and that is set a C

/->locale
LANG=C
LC_CTYPE="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_MESSAGES="C"
LC_ALL=C
/->
jose ramirez
Rick Garland
Honored Contributor

Re: warning secure ftp

Are you running a restricted FTP process for the account? Is it chrooted?

If so, have you copied all files over to the dir area for that restricted FTP account?

Jose Ramirez_6
Advisor

Re: warning secure ftp

Hi Rick.

yes i have ftp restricted.

I have the files under directory usr
jose ramirez
Chan 007
Honored Contributor

Re: warning secure ftp

Hi,

Add to your script
export LANG=C

Also ensure to debug by running with ksh -x <script name>, you may find that it gets set or not.

Else put in the .profile

Cheers ...007