similar to: UID -1 and --link-dest problem

When I'm running "rsync --compare-dest" on a local Linux volume (ext4) it works as expected (duplicate files not created) however when same commands with same options are run on NTFS USB drive (in my scenario below mounted to /share/external/sdt5) all the files are copied regardless if they have been updated or not. I have spent many hours trying to figure out what could be wrong and

I've looked around for a bug report on this problem and haven't seen one, so I apologize if this has already been discussed. I have a homegrown script which uses rsync to maintain daily backups of roughly twenty Redhat Linux systems running RH 7.2, 7.3, AS 3, and AS 4. As there are files with multiple links on the source systems, it is necessary to call rsync using the -H (--hard-links)

A friend and I mirror our music collections on each other's servers; between the two of us we have several hundred gigs of flac files. My friend runs Linux, I run FreeBSD. Recently we started playing with flac-1.1.4 (we had been using flac-1.1.2 previously) and I noticed something strange. flac-1.1.4, run with identical options on identical files, produces different output on the linux

http://bugzilla.netfilter.org/show_bug.cgi?id=612 Summary: conntrack returns src, dst, dport and sport all zeroed Product: libnfnetlink Version: unspecified Platform: i386 OS/Version: other Status: NEW Severity: major Priority: P1 Component: libnfnetlink AssignedTo: laforge at netfilter.org

Etx1 - First Internet Line - eth0 Ext2 - Second Internet line - eth2 LAN - Local Area Network - eth1 Other traffic - Ext1 -------+-------+--------------- Ext2 ---Web goes Here eth0 | |eth2 +-------+-------+ | ROUTER | +----+------+---+ |eth1 192.168.0.0/24 -----------------+ | 192.168.0.1/24------------------- - Gateway |

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

>>>>From what I see on their descriptions (site is in Chinese!), this is NOT a replacement of WINE. They place certain system services in the kernel and have compile kernel-module (.ko) to service them. ---- here is their plan: So, wine still could not solved the problem well. Out of such a concern, I suggested the idea and route of "Linux Compatible Kernel". Its objective

helow my goal is to install via kickstart a CentOS 7 NFS server but I fail to set the firewall rules at installation time. In my kickstart file I set: # Firewall configuration # ssh and NFS # Ports 111 and 875 are for rquotad firewall --enabled --ssh --service=nfs --port=111:tcp,111:upd,875:tcp,875:upd On the installed server,? /root/anaconda-ks.cfg contains: # Firewall configuration firewall

Hello!   I estimate vector error correction model (vecm) model. I have only one cointegratio relationship. I write :   joh.vecm.rls <- cajorls(joh.vecm, r=1) The output estimation is : Call: lm(formula = substitute(form1), data = data.mat) Coefficients:                up.d            expl.d        upd.d           r.d      ect1      -1.34e-01   4.55e+02   6.91e+00   2.43e+03 constant 

Hi, I was trying to make a mirror backup of a folder in my machine with the following command: rsync -avh --delete /source/ /destination But the extra files that where on "destination" didn't got deleted. Where as doing: rsync -avh --delete /source/ /destination/ worked as expected. I wonder if this is correct, or it shouldn't be like that. -------------- next part

On Sunday, January 26, 2020 3:58:31 PM CET Pete Biggs wrote: > > what does Centos 7 do with UPD packets having invalid checksums? > > By default I assume they are just dropped - that's what should happen. Hm that's what thought. > > Are such packets inevitably dropped? > > Applications can specifically disable checksum checking for the kernel > network stack

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is

> what does Centos 7 do with UPD packets having invalid checksums? By default I assume they are just dropped - that's what should happen. > > Are such packets inevitably dropped? Applications can specifically disable checksum checking for the kernel network stack on a per application basis, but the default is to check and drop if in error. > Does a network card drop them

First of all - disclaimer - I'm no network specialist, I just read and am interested in it. I may get things wrong!! > > > Both physical interfaces show the same. But does this mean it's on as in "rx- > checksumming: on" or off as in "tx-checksum-ipv4: off [fixed]"? As far as I understand it rx-checksum is the underlying wire checksumming - and from

https://bugzilla.samba.org/show_bug.cgi?id=10545 Summary: Rsync first time deletes files, second time it synchronates files with same name Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned

Hi, what does Centos 7 do with UPD packets having invalid checksums? Are such packets inevitably dropped? Does a network card drop them when it does checksum verification in hardware even before the packets go anywhere? In general, if someone were to send me UPD packets with invalid checksums over the internet, how far would such packets get? In particular, how likely it is that SRTP

> I would appreciate any insights over compiling R 3.4 with Intel MKL -- I have been successful until R 3.3.3 but now it stops complaining about pcre though it worked without Intel MKL as follows, I successfully built R-rc_2017-04-19_r72555.tar.gz with icc & MKL on centos 7 with this: # https://software.intel.com/en-us/articles/build-r-301-with-intel-c-compiler-and-intel-mkl-on-linux#

On Mon, 15 Dec 2003, jw schultz <jw@pegasys.ws> wrote: > OK, first pass on TODO complete. .... This hardlink bug report is nearly 21 months old... So I took a look at it using 2.5.7. See below. > BUGS --------------------------------------------------------------- > > Fix hardlink reporting 2002/03/25 > (was: There seems

On Wed, 5 Dec 2018 at 10:17, Gregory P. Ennis <PoMec at pomec.net> wrote: > > To all, > > I started the process of updating some of our systems from 7.5 to 7.6. > Most of the servers had no problems, but several of the desktops had > some difficulties. I was required to perform several yum commands to > update as much as possible in the format of yum update a* then b*

Last night, I was trying to install syslinux (5.01) to a SD card of mine, writing to a subdirectory to keep the layout neat: syslinux-5.01/linux# ./syslinux -i -d /boot /dev/mmcblk0p1 /dev/mmcblk0p1: No such file or directory The message is coming from do_open_file() in syslinux.c: the call to open() fails because the containing directory isn't present, and then it calls perror(opt.device).