search for: vol9

...> [Vol3] > ??????? path = /vol3 > ??????? invalid users = root > ??????? valid users = myuser > ??????? read only = no > > [Vol4] > ??????? path = /vol4 > ??????? invalid users = root > ??????? valid users = myuser > ??????? read only = no > > > [Vol9] > ??????? path = /vol9 > ??????? invalid users = root > ??????? valid users = myuser > ??????? read only = no > [VolP] > ??????? path = /volP > ??????? invalid users = root > ??????? valid users = myuser > ??????? read only = no > > [backup] > ???????...

...s instead getting back auto_direct which is the name of the automounter map we're using. The /etc/mnttab file has TWO entries for the auto-mounted filestore, like this: auto_direct /mailstore/messages/p autofs direct,ignore,dev=4740014 1184648400 crypt2.york.ac.uk:/vol/vol9/p /mailstore/messages/p nfs proto=tcp,xattr,dev=4700386 1184668792 Although there are two entries they have different device numbers. The mountpoint_get() function attempts to guard against this by checking the device number obtained matches that of the path being located. Ho...

...????? invalid users = root >> ??????? valid users = myuser >> ??????? read only = no >> >> [Vol4] >> ??????? path = /vol4 >> ??????? invalid users = root >> ??????? valid users = myuser >> ??????? read only = no >> >> >> [Vol9] >> ??????? path = /vol9 >> ??????? invalid users = root >> ??????? valid users = myuser >> ??????? read only = no >> [VolP] >> ??????? path = /volP >> ??????? invalid users = root >> ??????? valid users = myuser >> ??????? read...

...s instead getting back auto_direct which is the name of the automounter map we're using. The /etc/mnttab file has TWO entries for the auto-mounted filestore, like this: auto_direct /mailstore/messages/p autofs direct,ignore,dev=4740014 1184648400 crypt2.york.ac.uk:/vol/vol9/p /mailstore/messages/p nfs proto=tcp,xattr,dev=4700386 1184668792 Although there are two entries they have different device numbers. The mountpoint_get() function attempts to guard against this by checking the device number obtained matches that of the path being located. Ho...

...0029Z.vol3.difftar.gpg duplicity-full.20140531T230029Z.vol4.difftar.gpg duplicity-full.20140531T230029Z.vol5.difftar.gpg duplicity-full.20140531T230029Z.vol6.difftar.gpg duplicity-full.20140531T230029Z.vol7.difftar.gpg duplicity-full.20140531T230029Z.vol8.difftar.gpg duplicity-full.20140531T230029Z.vol9.difftar.gpg This is not good, because if the transfer is partial, they are not exploitable (I have to sync all files 10 to 19 ? and 100 to 199, 1000 to 1999 ? before transferring file 2). Thus, I added a --numeric-sort (-N) option to rsync, to transfer the files in the expected order. Patch atta...

Hello, I'm a bit desperate so I'm trying to seek help here. Many year ago, I built myself 2 file servers (5 disks enclosure for data, 2 disks enclosure for the OS) on a computer. It was running on Debian 7.11 for years without an issue and I was getting 75MB/95MB when transferring file from it to a Windows client, all having a 1gbs network card. https://i.ibb.co/N618Z4W/Debian-7.png