On Fri, Feb 07, 2020 at 08:23:43AM +0100, Michal Nowak via oi-dev wrote:
> On 02/07/20 06:46 AM, Marcel Telka wrote:
> > On Sun, Feb 02, 2020 at 01:28:12PM +0100, Michal Nowak via oi-dev wrote:
> > > On 02/02/20 08:15 AM, Marcel Telka wrote:
> > > > I noticed that rsync at dlc-origin stopped to wor
On 02/07/20 06:46 AM, Marcel Telka wrote:
On Sun, Feb 02, 2020 at 01:28:12PM +0100, Michal Nowak via oi-dev wrote:
On 02/02/20 08:15 AM, Marcel Telka wrote:
I noticed that rsync at dlc-origin stopped to work about 4 days ago:
rsync: failed to connect to dlc-origin.openindiana.org (91.194.75.37
On Sun, Feb 02, 2020 at 01:28:12PM +0100, Michal Nowak via oi-dev wrote:
> On 02/02/20 08:15 AM, Marcel Telka wrote:
> > I noticed that rsync at dlc-origin stopped to work about 4 days ago:
> >
> > rsync: failed to connect to dlc-origin.openindiana.org (91.194.75.37):
> > Connection timed out (14
On 02/02/20 08:15 AM, Marcel Telka wrote:
Hi,
I noticed that rsync at dlc-origin stopped to work about 4 days ago:
rsync: failed to connect to dlc-origin.openindiana.org (91.194.75.37):
Connection timed out (145)
rsync error: error in socket IO (code 10) at clientserver.c(127)
[Receiver=3.1.3
Hi,
I noticed that rsync at dlc-origin stopped to work about 4 days ago:
rsync: failed to connect to dlc-origin.openindiana.org (91.194.75.37):
Connection timed out (145)
rsync error: error in socket IO (code 10) at clientserver.c(127)
[Receiver=3.1.3]
Is this intentional?
Thanks
--
+-