1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FTP: related enhancements

Discussion in 'Suggestions' started by Steve Fabian, Mar 9, 2010.

  1. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    1/ Implement command COPY option /F when source is FTP:

    2/ After setting IFTP to ftp://jpsoft.com, the command

    *copy/[!descript.ion]/efgrv/netj/s/[d] ftp: .

    repeatedly reports the error:

    TCC: 550 Can't change directory to /incoming: Permission denied
    "/incoming/*"

    While I understand the indicated directory is inaccessible as a source,
    since it is intended for uploading plugins, I'd like to have some option for
    COPY to skip the error message. I think this might be achieved by making the
    "incoming" directory hidden...

    3/ Provide FTP support in @fstype[]

    4/ When a directory (tree) uses non-Windows file system, with properties
    known to TCC, e.g. Posix (Unix, Linux, BSD, etc.) optionally report
    attributes according to the file system. Allow the ATTRIB command to
    operate. Provide special mapping for attributes not available in Windows,
    e.g., X (eXecute) in Posix file systems (e.g. to enable execution of
    uploaded shell scripts).
    --
    Steve
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,856
    Likes Received:
    83
    Why do you think it's not already implemented? Is it not working for you?


    Doesn't have anything to do with "incoming" in particular; it's a matter of
    permissions -- and you don't have permission to access that directory. I
    don't think it's a generically good idea to suppress permission errors.


    Technically impossible -- unless you can convince the world to adopt a new
    FTP protocol. (Though I find it difficult to conceive of a reason why
    anyone would care.)


    to

    of

    Ditto.

    Rex Conn
    JP Software
     
  3. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,520
    Likes Received:
    4
    | ---Quote---
    || 1/ Implement command COPY option /F when source is FTP:
    | ---End Quote---
    | Why do you think it's not already implemented? Is it not working
    | for you?

    Never worked when source is FTP: and there are no files copied into some
    directory because of file selection criteria, e.g., date range. I presume
    the directories are created because they need to exist before the source
    directory can be searched for files to download, but they are not removed if
    nothing was copied into them. The /F works perfectly for local copies.

    | ---Quote---
    || 2/ After setting IFTP to ftp://jpsoft.com, the command
    ||
    || *copy/[!descript.ion]/efgrv/netj/s/[d] ftp: .
    ||
    || repeatedly reports the error:
    ||
    || TCC: 550 Can't change directory to /incoming: Permission denied
    || "/incoming/*"
    ||
    || While I understand the indicated directory is inaccessible as a
    || source, since it is intended for uploading plugins, I'd like to
    || have some
    || option for
    || COPY to skip the error message. I think this might be achieved by
    || making the "incoming" directory hidden...
    | ---End Quote---
    | Doesn't have anything to do with "incoming" in particular; it's a
    | matter of permissions -- and you don't have permission to access
    | that directory. I don't think it's a generically good idea to
    | suppress permission errors.

    I agree that permission errors should be displayed unless the user chooses
    to supress them. My issue here is exclusively with ftp://jpsoft.com. I'd
    like to be able to download recently posted files without error messages.
    For many months this was possible, but not anymore. I tried to put the
    directory name "incoming" into a file exclusion range, but that did not
    help. IIRC the "incoming" directory is for uploads, so maybe it could be
    moved to a different location? Made "hidden" in the Posix style?

    | ---Quote---
    || 3/ Provide FTP support in @fstype[]
    | ---End Quote---
    | Technically impossible -- unless you can convince the world to adopt
    | a new FTP protocol. (Though I find it difficult to conceive of a reason
    | why anyone would care.)

    Well, FTP has always been a poor protocol, having inherited the worst
    feature of the Unix cp command (by default copying a file creates a new
    file). Regardless, if it cannot done, we'll have to continue to live without
    it.

    | ---Quote---
    || 4/ When a directory (tree) uses non-Windows file system, with
    || properties known to TCC, e.g. Posix (Unix, Linux, BSD, etc.)
    || optionally report attributes according to the file system. Allow
    || the ATTRIB command
    | ---End Quote---
    | to
    |
    |
    | ---Quote---
    || operate. Provide special mapping for attributes not available in
    || Windows, e.g., X (eXecute) in Posix file systems (e.g. to enable
    || execution
    | ---End Quote---
    | of
    |
    |
    | ---Quote---
    || uploaded shell scripts).
    | ---End Quote---
    | Ditto.

    Too bad. Could RPC be used for this (and the previous) issue? I suppose one
    would have to guess at the type of the remote file system / OS ...

    BTW, note how the email system broke a single quotation into several, and
    left a few qoted words between the sections as if they weren't quoted.

    Thanks for the usual prompt response.
    --
    Steve
     

Share This Page