Hi! Am Sonntag, 2. September 2018 schrieb Thierry de Coulon: > Hello all, > > I understand this has nothing to do with trinity, but there seem to be people > on this list that understand this stuff more than I do. > > I've got an older machine (quad core) that I wanted to convert in a network > backup. It runs Jessie and mounts an nfs share on my main machine so that I > can copy important files. > > The problem occurs when I transfer bigger quantities of data (I mean several > GB, mostly in smaller files of a few hundred MB): > > - If the server runs Debian stretch, everything is fine. > > - If the server runs AntiX 17, the copy sooner or later hangs because the > server lost the network (the message I got is err_network_changed). there may > be another way but I solve the problem by restarting teh machine. > > Now, the question is this: AntiX 17 is based on stretch. It does not run > systemd, nor does it network manager. Network configuration is done with ceni > (method static, class auto). > > The exports file is the same in both cases (copied from Debian to AntiX). > > If anyone has a clue to give me where to look for this difference in > behaviour, I'd be glad! I like AntiX because of no systemd, but... What does dmesg say after the connection is lost? -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
