Hi, Thanks for your prompt reply.
I agree on the fact that cat doesn't catch the eof. So, you mean that the backup command sometimes doesn't send the eof (but the transferred file is complete and valid)? The backup command, which writes in the fifo is terminated, so nobody's trying to write in the fifo. How would I force to close the fifo? By simply removing it? Best Regrads, Fabrice -----Original Message----- From: Alexander V. Lukyanov [mailto:[EMAIL PROTECTED] Sent: vendredi, 18. avril 2008 09:58 To: Chatelain Fabrice Cc: [email protected] Subject: Re: [lftp] - sometimes doesn't catch eof On Wed, Apr 16, 2008 at 03:50:09PM +0200, Chatelain Fabrice wrote: > I'm running lftp to transfer backup file by reading a remote fifo > using fish protocol. > Sometimes, lftp doesn't get the eof and loops unfinitely by doing > timeout - reconnection, even if I configure lftp to never reconnect. I think it is "cat" command which do not catch eof. Is the fifo still open by someone for writing? > ---> #EXEC cat\ /dev/bkpfifo_1445918 > cat /dev/bkpfifo_1445918; echo '### 200' > //output of backup again > Creating information file (/image.data) for rootvg. > > Creating list of files to back up. > Backing up 4802 files > 4802 of 4802 files (100%) > //the backup is finished, so the eof should be send or catch.. > 0512-038 mksysb.FB.1445918: Backup Completed Successfully. > **** Timeout - reconnecting You see: there is no ### 200 message which would appear if and when cat terminates. That is cat is still running and someone holds the pipe open for writing. -- Alexander.
