I'm not certain whether this is a problem with ftp per se, or with the Linux version of BC3, but thought I would start by posting here.
I'm using version 3.07 under Ubuntu 8.04.1 along with openssh-server and sshfs so that I can synchronize the data on my two notebooks.
I also synchronize my primary data location with targets on two accessory drives on the main system.
When the secondary Ubuntu system is not on the network (or when I'm away from the network) I occasionally back up to the two accessory drives. If I accidentally click on one of the sftp sessions (the target being unavailable at this time) BC3 just wanders off into oblivion. Hitting the stop button on the toolbar does nothing. I have to kill the bcompare processes from the system monitor.
If I accidentally select a session which specifies one of the accesory target drives when they are not online, there is no problem. BC3 just tells me that the target is unavailable.
Is there a setting I can change that will prevent BC3 from behaving so badly when the sftp target isn't available?
I'm using version 3.07 under Ubuntu 8.04.1 along with openssh-server and sshfs so that I can synchronize the data on my two notebooks.
I also synchronize my primary data location with targets on two accessory drives on the main system.
When the secondary Ubuntu system is not on the network (or when I'm away from the network) I occasionally back up to the two accessory drives. If I accidentally click on one of the sftp sessions (the target being unavailable at this time) BC3 just wanders off into oblivion. Hitting the stop button on the toolbar does nothing. I have to kill the bcompare processes from the system monitor.
If I accidentally select a session which specifies one of the accesory target drives when they are not online, there is no problem. BC3 just tells me that the target is unavailable.
Is there a setting I can change that will prevent BC3 from behaving so badly when the sftp target isn't available?
Comment