similar to: Errors with program diagnostics (code 13) after rsync upgrade

Dear All, Found the issue. It was --progress. Without it the script runs fine under cron. Regards, Maxim On 11/17/24 03:04, Robin Lee Powell wrote: > If you were on Linux I'd say this is an SELinux issue. The FreeBSD > equivalent seems to be https://docs.freebsd.org/en/books/handbook/mac/ > > On Fri, Nov 15, 2024 at 04:08:27PM +0000, Maxim Usatov via rsync wrote: >>

On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote: > I assume code 13 is related to permissions, but given rsync is > started as root, why would this happen? The same rsync commands > worked on all previous versions of FreeBSD. It also fails with the > same error to a remote SSH host. If I run my rsync backup scripts > manually as root then everything works

Hi Ian, Tried without nice, xattrs, acls and hard-links - same error. Regards, Maxim Usatov On 11/15/24 17:42, Ian Z via rsync wrote: > On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote: > >> I assume code 13 is related to permissions, but given rsync is >> started as root, why would this happen? The same rsync commands >> worked on all previous

Hi, maybe ist a general Problem. i have the following question. Wheni create manually a DNS record with RSAT Tools there is no problem. The following steps i try to get automatically updates. The following steps i have done. - Remove the Computer from AD - Remove DNS Record (checked also with ldbsearch for the principal, nothing found) - Join the Computer back to

Have installed Redhat ES 3.1 and updated to samba-3.02-6.3E The PDC is solaris running PC netlink. Can join the domain if running samba 2.28. Have tried net oldjoin as well as net join but to no avail. Debug level 5 dump attached. Any help appreciated. [2004/03/16 11:56:53, 5] lib/debug.c:debug_dump_status(360) INFO: Current debug levels: all: True/5 tdb: False/0

Dear R users How should one approach diagnosing a regression on panel data? I am mostly talking about the "within" or Fixed Effects case. There are some panel-specific tests and diagnostics explained in require(plm) vignette("plm") But I was wondering if diagnostics on ordinary linear models (as explained here[1], for example) also apply to panel regressions. Perhaps someone

Dear all, I just wrote a script to have each of my three mcmc chins running on a different computer core to improve computation speed. To do it I use the function sfLapply from the package snowfall. Before using parallell computation, I did my diagnostic analyses just after the model updating, but now I have to save the coda before. Using the CODA package, it is possible to load the outputs in a

Hey folks, I looked back through the list archives and there are surprisingly few threads with "SSD" in the subject. In my new job I've been handed over a number of things that were outstanding with the previous Sys Admin, and one of them was an SSD that was suspect. I just plugged it into a diagnostics laptop to use the Linux Smart software to check it - and it all seems fine

HI, Andy, ON the RandomForest diagnostics plot, three lines were drawn. ON the help document of plot.randomForest, only the error rate and MSE are described. I dont know which line is which? Can you help me with that? Thanks so much! -- Sincerely, Changbin -- [[alternative HTML version deleted]]

I am hoping that some one might be to tell me whether there are any functions that produce influence measures for lme /nlme objects (i.e those suggested by Lesaffre and Verbeke or Langford and Lewis for multilevel models). Thanks in advance. ----------------------------------------------- Anthony A. Pezzola apezzola@uc.cl (02) 354-7823 Profesor de Ciencia Política Instituto de Ciencia

https://bugzilla.netfilter.org/show_bug.cgi?id=1353 Bug ID: 1353 Summary: DIAGNOSTICS section of manpage doesn't list xtable lock exit code 4 Product: iptables Version: CVS (please indicate timestamp) Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5

Hi, llvm-ld currently does not have the diagnostics framework. PIC16 does not support recursion and we want to diagnose that in llvm-ld and issue an error. Is that doable with ease (as far as the flashing an error message is concerned)? - Sanjiv

Hi, lld doesnot have a Diagnostics interface, It uses llvm::errs() to display errors after linking has been done. I think the Diagnostics interface follow similiar interface patterns as followed by clang (using Diagnostic td files). What do you think ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation

Ping ? On 10/4/2013 10:41 PM, Shankar Easwaran wrote: > Hi, > > lld doesnot have a Diagnostics interface, It uses llvm::errs() to > display errors after linking has been done. > > I think the Diagnostics interface follow similiar interface patterns > as followed by clang (using Diagnostic td files). > > What do you think ? > > Thanks > > Shankar Easwaran

On Mon, Oct 7, 2013 at 3:36 PM, Rui Ueyama <ruiu at google.com> wrote: > I think having diagnostics interface similar to Clang's would be good. Much like the options library, it has been a long-term desire to refactor all of the Clang diagnostics infrastructure into a largely independent library that could be used by lots of different tools, Clang, LLD, and even some internal tools

On Fri, Nov 15, 2013 at 11:19 AM, Umesh Kalappa <umesh.kalappa0 at gmail.com> wrote: > Hi Aaron, > >>>Why is getLastArgIntValue being called twice in the first place? > > It has been called from the getOptimizationLevel() ,which in turn called by > methods like ParseCodeGenArgs() and ParseLangArgs(), > > where method getOptimizationLevel() register the

> As Chad pointed, it's likely that this requires a non-trivial > refactoring. I don't have particularly bright ideas on solving it, but > I'm uncomfortable adding the flag at the arg level because it kind of > encourages lazy design when handling args. Perhaps looking into ways > the code could be refactored so that getOptimizationLevel() is only > called once (and

On Monday, 16 April 2018 11:48:08 CEST Richard W.M. Jones wrote: > Some filesystems fall back silently to read-only if there are problems > such a dirty filesystem and an unrecoverable journal. Almost all > conversions involve writing to the root filesystem, so these will > inevitably fail later on with a strange error message. > > Test the root filesystem is writable by

On Fri, Oct 30, 2020 at 5:03 PM Xiangling Liao via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > I noticed that there are some diagnostics discrepancies between clang and gcc related to `__attribute__((constructor(n)))` and `__attribute__((destructor(n)))`. > > [clang] > It seems priorities >65535 and <0 on ctor/dtor functions are ignored and are set

Hi Guys, Has anyone successfully installed and ran the Dell Online Diagnostics for Centos 6.2? RHEL 6 is a listed as a supported OS, but it appears the install.sh shell script says it is unsupported. Any ideas? Thanks, Brad This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail