peasth...@shaw.ca wrote: > Bob Proulx wrote: > > Is there a constraint that you must use ftp? ... > > ETHNO has FTP and SSH.Send but not rsync. SSH.Send requires > painfully more time than FTP does. To obtain rsync, the client > system would have to be changed.
I think hacking the ftp backend will always be problematic. The ftpd on the remote end doesn't have the same information that you want it to have and I think trying to force it won't be satisfactory. Is it possible to script a file transfer process? Put the file you want into an incoming dropbox first. Then upload an additional control file along with it. A process listens through inotify on the receiving end for the control file. In the control file add an integrity check for the original file just for safety sake. When control files appear the incoming handling process reads the file and acts upon the instructions included in the file. That type of thing would allow you to keep using ftp or whatever raw file transfer protocol you wish to use but then on the receiving side act upon it to handle the file in whatever way you desire. It could set the permissions and install it into whatever location the control file specified. (I know you said you were using a secure network and so security was not an issue. But at some point in the future it would be easy to convert this to using gpg signed files and then it would be secure even over an insecure network. A plus for a future expansion.) Bob
signature.asc
Description: Digital signature
