Re: [gentoo-user] strange eix-sync
On Sat, Jul 13, 2013 at 7:40 AM, meino.cra...@gmx.de wrote: /dev/root on / type ext4 (rw,noatime,user_xattr,commit=60,barrier=1,data=ordered) You don't have a separate mount for /tmp, so the above would be pertinent. And it shows support for xattr, so you should be good -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3
Re: [gentoo-user] strange eix-sync
On Sat, Jul 13, 2013 at 1:19 AM, meino.cra...@gmx.de wrote: How can I pratically proof the availability of xattr on the filesystem of /tmp -- beside checking the kernel config. Is your /tmp a tmpfs? What's the output of 'mount' please? -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3
Re: [gentoo-user] strange eix-sync
Douglas J Hunley doug.hun...@gmail.com [13-07-13 13:36]: On Sat, Jul 13, 2013 at 1:19 AM, meino.cra...@gmx.de wrote: How can I pratically proof the availability of xattr on the filesystem of /tmp -- beside checking the kernel config. Is your /tmp a tmpfs? What's the output of 'mount' please? -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3 beaglebone:/rootmount rootfs on / type rootfs (rw) /dev/root on / type ext4 (rw,noatime,user_xattr,commit=60,barrier=1,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=125556k,nr_inodes=31389,mode=755) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755) openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc) cpuset on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu) cpuacct on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct) memory on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) devices on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) freezer on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) blkio on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) perf_event on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85) beaglebone:/tmpdf -h . Filesystem Size Used Avail Use% Mounted on /dev/root15G 5.6G 8.3G 41% / I also removed (as an experiement) the acl and xattr use flags from rsyncno success (the original settings only remove the xattr-flags).
Re: [gentoo-user] strange eix-sync
On 13 July 2013, at 12:40, meino.cra...@gmx.de wrote: ... I also removed (as an experiement) the acl and xattr use flags from rsyncno success (the original settings only remove the xattr-flags). Again, Meino, you're not stating clearly enough what you've done. Did you unset these USE flags and remerge the package? I would be inclined to unset these USE flags globally and remerge all packages which use them, but I don't use ACLs or extended attributes, so this might be bad advice for someone who relies upon them. Stroller.
Re: [gentoo-user] strange eix-sync
Stroller strol...@stellar.eclipse.co.uk [13-07-12 00:51]: On 11 July 2013, at 19:58, meino.cra...@gmx.de wrote: ... beaglebone:/rootKrm -v rm: remove regular empty file ‘/tmp/foobar123’? yes removed ‘/tmp/foobar123’ ... Everything was done as root. I think this is the output of `rm -vi $file` not `rm -v $file` - this suggests you have at least one alias enabled. This is probably a red herring, but I would try everything again ensuring no aliases or other user shell customisations enabled. Stroller. How can I pratically proof the availability of xattr on the filesystem of /tmp -- beside checking the kernel config. From the point of view of rsync -- so to say? After this update it stops working. In the meanwhile I had reinstalled all old versions with no success 1373166229: Started emerge on: Jul 07, 2013 05:03:48 1373166229: *** emerge --oneshot --keep-going --verbose =sys-fs/dosfstools-3.0.20-r1 =net-misc/rsync-3.0.9-r3 =app-admin/eselect-1.3.6 =net-misc/ntp-4.2.6_p5-r3 =virtual/udev-200 1373166331: emerge (1 of 5) sys-fs/dosfstools-3.0.20-r1 to / 1373166332: === (1 of 5) Cleaning (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166333: === (1 of 5) Compiling/Merging (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166409: === (1 of 5) Merging (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166432: AUTOCLEAN: sys-fs/dosfstools:0 1373166432: === Unmerging... (sys-fs/dosfstools-3.0.20) 1373166447: unmerge success: sys-fs/dosfstools-3.0.20 1373166465: === (1 of 5) Post-Build Cleaning (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166465: ::: completed emerge (1 of 5) sys-fs/dosfstools-3.0.20-r1 to / 1373166465: emerge (2 of 5) net-misc/rsync-3.0.9-r3 to / 1373166465: === (2 of 5) Cleaning (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166466: === (2 of 5) Compiling/Merging (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166811: === (2 of 5) Merging (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166828: AUTOCLEAN: net-misc/rsync:0 1373166828: === Unmerging... (net-misc/rsync-3.0.9-r2) 1373166843: unmerge success: net-misc/rsync-3.0.9-r2 1373166861: === (2 of 5) Post-Build Cleaning (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166861: ::: completed emerge (2 of 5) net-misc/rsync-3.0.9-r3 to / 1373166861: emerge (3 of 5) app-admin/eselect-1.3.6 to / 1373166861: === (3 of 5) Cleaning (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166862: === (3 of 5) Compiling/Merging (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166904: === (3 of 5) Merging (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166929: AUTOCLEAN: app-admin/eselect:0 1373166929: === Unmerging... (app-admin/eselect-1.3.5) 1373166944: unmerge success: app-admin/eselect-1.3.5 1373166960: === (3 of 5) Post-Build Cleaning (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166960: ::: completed emerge (3 of 5) app-admin/eselect-1.3.6 to / 1373166961: emerge (4 of 5) net-misc/ntp-4.2.6_p5-r3 to / 1373166961: === (4 of 5) Cleaning (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373166963: === (4 of 5) Compiling/Merging (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167738: === (4 of 5) Merging (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167774: AUTOCLEAN: net-misc/ntp:0 1373167774: === Unmerging... (net-misc/ntp-4.2.6_p5-r2) 1373167792: unmerge success: net-misc/ntp-4.2.6_p5-r2 1373167815: === (4 of 5) Post-Build Cleaning (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167815: ::: completed emerge (4 of 5) net-misc/ntp-4.2.6_p5-r3 to / 1373167816: emerge (5 of 5) virtual/udev-200 to / 1373167816: === (5 of 5) Cleaning (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167816: === (5 of 5) Compiling/Merging (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167841: === (5 of 5) Merging (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167855: AUTOCLEAN: virtual/udev:0 1373167855: === Unmerging... (virtual/udev-197-r3) 1373167870: unmerge success: virtual/udev-197-r3 1373167888: === (5 of 5) Post-Build Cleaning (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167888: ::: completed emerge (5 of 5) virtual/udev-200 to / 1373167888: *** Finished. Cleaning up... 1373167905: *** exiting successfully. 1373167914: *** terminating. 1373248019: Started emerge on: Jul 08, 2013 03:46:59 1373248019: ***
Re: [gentoo-user] strange eix-sync
On Wed, Jul 10, 2013 at 12:06 PM, meino.cra...@gmx.de wrote: is this a newly added feature, which is needed? Since three days (about) before it works like a charm. Beside updateing my system, I did nothing to change the filesytem (ext4 if I remember correctly) or such ... Any ideas, what triggers this sudden problem? Honestly, it's just an educated guess from the output you pasted. I have xattr support on all my filesystems, so, I've never seen this nor do I know if it's something newly required or what. Also note that I'm assuming your /tmp is mode 1777 ... is it? -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3
Re: [gentoo-user] strange eix-sync
On 9 July 2013, at 18:28, meino.cra...@gmx.de wrote: ... receiving incremental file list timestamp.chk rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) I can't say the problem is related to xattrs, but when posting an error with a message like this you need to demonstrate, for example, that the /tmp directory exists and that you can write to it. I mean, it's pretty obvious that you'd get this error if the directory wasn't writable, right? So posting here you need to *show* it's writable. So please post the output of: ls -ld /tmp/ ls -l /tmp/ touch /tmp/foobar123 chmod 777 /tmp/foobar123 ls -l /tmp/foobar123 rm -v /tmp/foobar123 I would also try testing whether you can sync using the `emerge --sync` command, instead. I would guess that you're escalating to root permissions when using emerge and that the eix user has insufficient write permissions for some reason. No offence, mate, but a Gentoo user shouldn't need to be told this. You surely have a couple of years of Linux experience, so you know how to create and list a file; even if you don't know the `chmod` command, you must know what permissions are and that they sometimes prevent an unprivileged user from doing stuff. Aren't you even curious to know if the /tmp directory exists? Page 1 of How to Ask Questions The Smart Way says to tell us what you've done to investigate the problem so far. I can't promise that the steps I've suggested will help identify or fix the problem, but they definitely need doing to show the filesystem exists and doesn't have a write-protect switch accidentally flipped - failure to provide this information implies you're sitting helplessly at home waiting for us to tell you all the answers, even the basics. Stroller.
Re: [gentoo-user] strange eix-sync
Stroller strol...@stellar.eclipse.co.uk [13-07-11 18:12]: On 9 July 2013, at 18:28, meino.cra...@gmx.de wrote: ... receiving incremental file list timestamp.chk rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) I can't say the problem is related to xattrs, but when posting an error with a message like this you need to demonstrate, for example, that the /tmp directory exists and that you can write to it. I mean, it's pretty obvious that you'd get this error if the directory wasn't writable, right? So posting here you need to *show* it's writable. So please post the output of: ls -ld /tmp/ ls -l /tmp/ touch /tmp/foobar123 chmod 777 /tmp/foobar123 ls -l /tmp/foobar123 rm -v /tmp/foobar123 I would also try testing whether you can sync using the `emerge --sync` command, instead. I would guess that you're escalating to root permissions when using emerge and that the eix user has insufficient write permissions for some reason. No offence, mate, but a Gentoo user shouldn't need to be told this. You surely have a couple of years of Linux experience, so you know how to create and list a file; even if you don't know the `chmod` command, you must know what permissions are and that they sometimes prevent an unprivileged user from doing stuff. Aren't you even curious to know if the /tmp directory exists? Page 1 of How to Ask Questions The Smart Way says to tell us what you've done to investigate the problem so far. I can't promise that the steps I've suggested will help identify or fix the problem, but they definitely need doing to show the filesystem exists and doesn't have a write-protect switch accidentally flipped - failure to provide this information implies you're sitting helplessly at home waiting for us to tell you all the answers, even the basics. Stroller. Hi Stroller, so here it comes Script started on Thu Jul 11 20:53:07 2013 beaglebone:/rootKls -ld /tmp/ drwxrwxrwt 13 root root 4096 2000-01-01 01:00 0m30;42m/tmp/0m beaglebone:/rootKls -l /tmp/ total 10412 -rw-r--r-- 1 root root 22 2012-12-27 12:55 02locale.org -rw--- 1 mccramer users 27785 2012-12-22 20:22 alsa-info.YEBlUiUDLs -rwxr-xr-x 1 mccramer users 1313576 2012-12-24 14:27 0m01;32mbib12.txt0m -rw-r--r-- 1 root root1313576 2013-05-18 18:59 bib12.txt.bak -rw-r--r-- 1 root root 56 2013-01-10 08:21 boost drwxr-xr-x 2 mccramer users 4096 2013-04-07 10:12 01;34mhsperfdata_mccramer0m -rw-r--r-- 1 root root 12452 2013-05-17 03:49 log -rw--- 1 root root 0 2012-12-24 09:06 manpages-checkszlVA drwx-- 2 mccramer users 4096 2012-12-26 08:58 01;34mmc-mccramer0m drwx-- 2 root root 4096 2012-12-27 11:24 01;34mmc-root0m -rw-r--r-- 1 root root3660737 2012-12-24 14:49 pkgfiles-2012-12-24.txt -rw-r--r-- 1 root root3800288 2013-05-18 15:24 pkgfiles-2013-05-18.txt -rw-r--r-- 1 root root 2402 2012-12-27 17:27 pkgneon.txt -rw-r--r-- 1 root root 122383 2012-12-26 17:47 pkgremoval.txt -rw-r--r-- 1 root root 1757 2013-01-13 10:33 pkgremoval4.txt -rw-r--r-- 1 root root 1704 2012-12-25 07:24 pkgtypes.txt drwxrwxr-x 8 portage portage4096 2013-07-05 19:21 01;34mportage0m drwx-- 2 mccramer users 4096 2013-01-18 04:46 01;34mpulse-2L9K88eMlGn70m drwx-- 2 root root 4096 2013-01-18 04:46 01;34mpulse-CcctT9RwKSB10m drwx-- 2 mccramer users 4096 2013-05-01 18:54 01;34mpulse-FebW397VI5uG0m drwx-- 2 root root 4096 2013-01-09 23:00 01;34mpulse-PKdhtXMmr18n0m -rw-r--r-- 1 root root 310061 2012-12-27 08:59 rempkgfiles.txt -rw-r--r-- 1 root root 2155 2012-12-27 08:56 rempkgs.txt drwxr-xr-x 3 root root 4096 2013-05-23 02:54 01;34mvim.build0m -rw-r--r-- 1 root root501 2013-05-18 19:12 x beaglebone:/rootKtouch /tmp/foobar123 beaglebone:/rootKls -l /tmp/foobar123 -rw-r--r-- 1 root root 0 2013-07-11 20:53 /tmp/foobar123 beaglebone:/rootKchmod 777 /tmp/foobar123 beaglebone:/rootKls -l /tmp/foobar123 -rwxrwxrwx 1 root root 0 2013-07-11 20:53 0m01;32m/tmp/foobar1230m beaglebone:/rootKrm -v /tmp/foobar123 rm: remove regular empty file ‘/tmp/foobar123’? yes removed ‘/tmp/foobar123’ beaglebone:/rootKemerge --sync 0;emerge Starting rsync with rsync://91.186.30.235/gentoo-portage... Checking server timestamp ... Welcome to boobie.gentoo.org / rsync.gentoo.org Server Address : 91.186.30.235 Contact Name : mirror-ad...@gentoo.org Hardware : 2 x Intel(R) Xeon(R) CPU 3050 @ 2.13GHz, 3958MB RAM Sponsor: EUKhost, Maidenhead, England Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Sun Apr 1 01:05:34 UTC 2012 receiving incremental file list timestamp.chk
Re: [gentoo-user] strange eix-sync
On 11 July 2013, at 19:58, meino.cra...@gmx.de wrote: ... beaglebone:/rootKrm -v rm: remove regular empty file ‘/tmp/foobar123’? yes removed ‘/tmp/foobar123’ ... Everything was done as root. I think this is the output of `rm -vi $file` not `rm -v $file` - this suggests you have at least one alias enabled. This is probably a red herring, but I would try everything again ensuring no aliases or other user shell customisations enabled. Stroller.
Re: [gentoo-user] strange eix-sync
On Tue, Jul 9, 2013 at 1:28 PM, meino.cra...@gmx.de wrote: rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) You don't have POSIX ACL )xattr) support on whatever fs you have for /tmp ? -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3
Re: [gentoo-user] strange eix-sync
Douglas J Hunley doug.hun...@gmail.com [13-07-10 17:24]: On Tue, Jul 9, 2013 at 1:28 PM, meino.cra...@gmx.de wrote: rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) You don't have POSIX ACL )xattr) support on whatever fs you have for /tmp ? -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3 Hi Douglas, is this a newly added feature, which is needed? Since three days (about) before it works like a charm. Beside updateing my system, I did nothing to change the filesytem (ext4 if I remember correctly) or such ... Any ideas, what triggers this sudden problem? Best regards, mcc
[gentoo-user] strange eix-sync
Hi, eix-syncing my Beaglebone results in some strange output and no eix-sync at all. Especially those rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) are mysterious. I added the complete log below. I dont want to trigger a ban of my IP for too many /try/change/try/change...cycles...so better to ask the pros... ;) Thank you very much in advance for any help! Best regards, mcc beaglebone:/rooteix-sync * Running emerge --sync Starting rsync with rsync://140.211.166.189/gentoo-portage... Checking server timestamp ... Welcome to bobolink.gentoo.org / rsync.gentoo.org Server Address : 140.211.166.189 Contact Name : mirror-ad...@gentoo.org Hardware : 4 x Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 3960MB RAM Sponsor: Gentoo Linux, Open Source Lab, Corvallis, OR, USA Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Sun Apr 1 01:06:12 UTC 2012 receiving incremental file list timestamp.chk rsync: failed to set permissions on /tmp/.tmpNBwK63.n6Acda: Function not implemented (38) Number of files: 1 Number of files transferred: 1 Total file size: 32 bytes Total transferred file size: 32 bytes Literal data: 32 bytes Matched data: 0 bytes File list size: 27 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 98 Total bytes received: 646 sent 98 bytes received 646 bytes 212.57 bytes/sec total size is 32 speedup is 0.04 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] Retrying... Starting retry 1 of 6 with rsync://88.198.83.250/gentoo-portage Checking server timestamp ... rsync: failed to connect to 88.198.83.250 (88.198.83.250): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9] Retrying... Starting retry 2 of 6 with rsync://209.177.148.226/gentoo-portage Checking server timestamp ... Welcome to magpie.gentoo.org / rsync.gentoo.org Server Address : 209.177.148.226, 2607:f740:0:29:230:48ff:fef8:a064 Contact Name : mirror-ad...@gentoo.org Hardware : 4 x Intel(R) Xeon(R) CPU X3330 @ 2.66GHz, 3957MB RAM Sponsor: Host Virtual, San Jose, CA, USA Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Mon Sep 17 20:05:05 UTC 2012 receiving incremental file list timestamp.chk rsync: failed to set permissions on /tmp/.tmpd7GTJG.cbU5Pd: Function not implemented (38) Number of files: 1 Number of files transferred: 1 Total file size: 32 bytes Total transferred file size: 32 bytes Literal data: 32 bytes Matched data: 0 bytes File list size: 27 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 98 Total bytes received: 661 sent 98 bytes received 661 bytes 303.60 bytes/sec total size is 32 speedup is 0.04 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] Retrying... Starting retry 3 of 6 with rsync://91.186.30.235/gentoo-portage Checking server timestamp ... Welcome to boobie.gentoo.org / rsync.gentoo.org Server Address : 91.186.30.235 Contact Name : mirror-ad...@gentoo.org Hardware : 2 x Intel(R) Xeon(R) CPU 3050 @ 2.13GHz, 3958MB RAM Sponsor: EUKhost, Maidenhead, England Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Sun Apr 1 01:05:34 UTC 2012 receiving incremental file list timestamp.chk rsync: failed to set permissions on /tmp/.tmpFmdYeR.y0q8Nx: Function not implemented (38) Number of files: 1 Number of files transferred: 1 Total file size: 32 bytes Total transferred file size: 32 bytes Literal data: 32 bytes Matched data: 0 bytes File list size: 27 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 98 Total bytes received: 620 sent 98 bytes received 620 bytes 478.67 bytes/sec total size is 32 speedup is 0.04 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9] Retrying... Starting retry 4 of 6 with rsync://88.198.83.249/gentoo-portage Checking server timestamp ... rsync: failed to connect to 88.198.83.249 (88.198.83.249): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9] Retrying... Starting retry 5 of 6 with rsync://[2607:f740:0:29:230:48ff:fef8:a064]/gentoo-portage Checking server timestamp ... rsync: failed to connect to
