search for: posixly_correct

..._OBJ) +$(T_UNSAFE_EXE): $(T_UNSAFE_OBJ) $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $(T_UNSAFE_OBJ) $(LIBS) # I don't like these rules because CVS can skew the timestamps and @@ -157,14 +162,14 @@ test: check # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) - POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync$(EXEEXT) srcdir="$(srcdir)" $(srcdir)/runtests.sh + POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/$(RSYNC_EXE) srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a ver...

...t; $(srcdir)/proto.h clean: cleantests - rm -f *~ $(OBJS) rsync $(TLS_OBJ) $(CHECK_PROGS) + rm -f *~ $(OBJS) $(TLS_OBJ) $(CHECK_PROGS) cleantests: rm -rf ./testtmp* @@ -151,14 +153,14 @@ test: check # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) - POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="$(srcdir)" $(srcdir)/runtests.sh + POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync$(EXEEXT) srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a version in...

...lk them into fixing it. You should request that the same change be made to cygwin's rsh. Work arounds are: - Specify --rsh="rsh --" option to rsync (this should work if they fixed the bug in how the -- option is parsed that was present back when ssh was similarly broken). - Export POSIXLY_CORRECT in your environment. This will prevent all commands from reordering their command-line arguments and affects other program aspects, so this is probably not a good way to go. - Create a shell script that exports POSIXLY_CORRECT and then execs the real rsh with the supplied command-line args. Renam...

On 2019-08-17 08:42, Jonathan Billings wrote: > On Aug 17, 2019, at 9:25 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> I like this one. Long-long ago it was one of the ?tricky? questions at the UNIX admin test (exam). Basically, no matter how devastating that may sound, the command only will remove what is (alphabetically it was that time) before /dev/[root_device].

...; if we need any helper programs it # should depend on them too. # We try to run the scripts with POSIX mode on, in the hope that will # catch Bash-isms earlier even if we're running on GNU. Of course, we # might lose in the future where POSIX diverges from old sh. check: all $(CHECK_PROGS) POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="$(srcdir)" $(srcdir)/runtests.sh # This does *not* depend on building or installing: you can use it to # check a version installed from a binary or some other source tree, # if you want. installcheck: $(CHECK_PROGS) POSIXLY_CORRECT=1 TOOLDI...

...> on throw-away system first ;-) - so I can copy and paste what I got to this > email. GNU coreutils also has that feature, you can't run 'rm -rf /' there either, you need to run it with --no-preserve-root. This was added to Coreutils in 2003. Be careful in FreeBSD, if you have POSIXLY_CORRECT defined, it will let you rm -rf /. -- Jonathan Billings <billings at negate.org>

...m first ;-) - so I can copy and paste what I got to this >> email. > > GNU coreutils also has that feature, you can't run 'rm -rf /' there > either, you need to run it with --no-preserve-root. This was added to > Coreutils in 2003. Be careful in FreeBSD, if you have POSIXLY_CORRECT > defined, it will let you rm -rf /. Yes, I know... and I'm far from "admiring foolproofness" of which there is none... as [on FreeBSD] rm -rf /* does remove everything but "immutable" files, directories,... You can not make anything fool proof (unless it is android...

hello, I have a following problem while using rsync: rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) it was coused by command rsync -r source/ dest/ -e rsh I use rsync-2.6.0 with rsh. What bothers me is that folowing problem apears time to time. I already checked the location of rsync on both machines, both

I'm running 'make check' to run the testsuite, and I did it this way so the ssh-basic test would run: # export rsync_enable_ssh_tests=yes # make check I did set up ssh so this would run, and here's what I get for output: POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="." ./runtests.sh ============================================================ ./runtests.sh running in /usr/src/redhat/BUILD/rsync-2.5.6_no_segvpatch rsync_bin=/usr/src/redhat/BUILD/rsync-2.5.6_no_segvpatch/rsync srcdir=. testuser=...

Hi, Not sure when this stopped working, because I'm sure it used to. This is the cygwin build of rsync, with the standard cygwin rsh (which is a fairly old GNU inetutils 1.3.2). ~=> rsync --rsh=rsh -vv bibble: opening connection using rsh bibble rsync --server --sender -vvr . rsh: unknown option -- server Try `rsh --help' for more information. rsync: connection unexpectedly closed

https://bugzilla.netfilter.org/show_bug.cgi?id=1254 Bug ID: 1254 Summary: nft commandline tool can't parse negative priority values. Product: nftables Version: unspecified Hardware: x86_64 OS: Ubuntu Status: NEW Severity: normal Priority: P5 Component: nft

...IRSTACK=() EUID=0 GROUPS=() HOME=/root HOSTNAME=server HOSTTYPE=i386 IFS=' ' LANG=de_DE@euro LANGUAGE=de_DE:de:en_GB:en LOGNAME=root MACHTYPE=i386-pc-linux-gnu OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin PIPESTATUS=([0]="0") POSIXLY_CORRECT=y PPID=25970 PS4='+ ' PWD=/root SHELL=/bin/sh SHELLOPTS=braceexpand:hashall:interactive-comments:posix SHLVL=2 TERM=dumb UID=0 set as root: BASH=/bin/bash BASH_VERSINFO=([0]="2" [1]="05b" [2]="0" [3]="1" [4]="release" [5]="i386-pc-li...

...rc1/testtmp.hardlinks/to/ : No such file or directory (1) unexpected EOF in read_timeout ----- hardlinks log ends FAIL hardlinks For comparison, I also ran the Apple-supplied version of rsync through the test suite: % /usr/bin/rsync --version rsync version 2.3.1 protocol version 20 ... env POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=/usr/bin/rsync srcdir=. ./runtests.sh ... ----- daemon-gzip-download log follows building configuration /local/build/rsync-2.5.5rc1/testtmp.daemon-gzip-download/ test-rsyncd.conf Running: "/usr/local/bin/rsync-2.3.1 -avvz localhost::test-from/ "/local/build/r syn...

https://bugzilla.samba.org/show_bug.cgi?id=10951 Bug ID: 10951 Summary: Emtpy parameter triggers unwanted behavior, but no error message Product: rsync Version: 3.1.0 Hardware: x64 OS: Linux Status: NEW Severity: major Priority: P5 Component: core Assignee:

...problem that you might notice if you have had your coffee already this morning is that it is attempting to cat the file WITH quotations. The line that causes the problem is line 233 of runtests.sh: echo "SKIP $testbase (`cat \"$scratchdir/whyskipped\"`)" This is a POSIXLY_CORRECT behavior on part of the OpenBSD sh according to the sh man page which has a specific section on it: o Occurrences of \" inside double quoted `..` command substitutions. In POSIX mode, the \" is interpreted when the command is interpreted; in non-POSIX mode, the b...

...prompt A few times it will work. It depends a bit on what code is being executed in the readpassphrase function, at openbsd-compat/readpassphrase.c in the openssh code. It has been verified that exec'ing again /bin/sh with --posix before running sftp, or exporting the environment variable POSIXLY_CORRECT before the "ssh user at localhost" step prevents the problem. So, while the problem appears to be kind of expected, it is being reported in case it was not meant to happen. Originally reported in Red Hat bugzilla [1]. This is rare race condition, where we stuck in the code openbsd-compa...

...ue Dec 24 08:42:04 2002 +++ rsync-2.5.6/batch.c Fri Feb 21 16:45:47 2003 @@ -8,6 +8,10 @@ #include "rsync.h" #include <time.h> +#ifndef S_IEXEC +# define S_IEXEC 0x040 +#endif + extern char *batch_prefix; struct file_list *batch_flist; -------------- next part -------------- POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="." ./runtests.sh ============================================================ ./runtests.sh running in /boot/home/devel/rsync-2.5.6 rsync_bin=/boot/home/devel/rsync-2.5.6/rsync srcdir=. testuser=revol os=BeOS patrick 5.0.4 1000...

...ls.c: In function `list_file': tls.c:124: warning: int format, uid_t arg (arg 4) tls.c:124: warning: int format, gid_t arg (arg 5) tls.c:124: warning: int format, long int arg (arg 6) gcc -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -o tls tls.o syscall.o lib/permstring.o -lresolv -lsocket -lnsl POSIXLY_CORRECT=1 TLS=`pwd`/tls rsync_bin=`pwd`/rsync srcdir="." ./runtests.sh ============================================================ ./runtests.sh running in /space/appsrc/rsync-2.5.2 rsync_bin=/space/appsrc/rsync-2.5.2/rsync srcdir=. scratchbase=/space/appsrc/rsync-2.5.2/testtmp P...

...argc' getgroups.c:34: warning: unused parameter `argv' gcc -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -o getgroups getgroups.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c trimslash.c -o trimslash.o gcc -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -o trimslash trimslash.o syscall.o POSIXLY_CORRECT=1 TOOLDIR=`pwd` rsync_bin=`pwd`/rsync srcdir="." ./runtests.sh ============================================================ ./runtests.sh running in /Volumes/local/tmp/rsync-2.5.5 rsync_bin=/Volumes/local/tmp/rsync-2.5.5/rsync srcdir=. testuser=root os=Darwin diderot.local...

...; in + write_script (destdir // "run-and-log.sh") script_run_and_log; + + (* Create the fake sudo support. *) + do_mkdir (destdir // "fake-bin"); + let fake_sudo = "\ +#!/bin/bash + +SCRIPTNAME=fake-sudo + +ARGS_SHORT=\"EHiu:\" +ARGS_LONG=\"\" +TEMP=`POSIXLY_CORRECT=1 getopt ${ARGS_SHORT:+-o $ARGS_SHORT} ${ARGS_LONG:+--long $ARGS_LONG} \ + -n \"$SCRIPTNAME\" -- \"$@\"` +if [ $? != 0 ]; then echo \"$SCRIPTNAME: terminating...\" >&2 ; exit 1 ; fi +eval set -- \"$TEMP\" + +preserve_env= +set_home= +login_shell= +...