search for: dstfile

...at btrfs could otherwise execute and with slight change of circumstances will actually execute fine. Imagine we have a btrfs on /dev/mapper/foobar with subvols /foo and /bar. Let’s also imagine top of said fs in mounted at /mnt. In this case, a cross-subvol clone of /mnt/foo/srcfile to /mnt/bar/dstfile will succeed. However, if only the individual subvols were mounted like this: /dev/mapper/foobar on /mnt (subvol=foo) /dev/mapper/foobar on /mnt2 (subvol=bar), then a clone of /mnt/srcfile to /mnt2/dstfile will fail with EXDEV even though it is otherwise equal to the former clone operation. W...

...************************************ #!/usr/bin/perl -w $aginame="conf-background.agi"; use File::Copy cp; use Asterisk::AGI; $AGI = new Asterisk::AGI; my %input = $AGI->ReadParse(); print STDERR "Dialing your number\n"; $srcfile="/tmp/mycall"; $dstfile="/var/spool/asterisk/outgoing/mycall"; open(MYCALL,">$srcfile") || die "Cant't open file :$srcfile $!\n"; print MYCALL "Channel:Zap/1/13\n"; print MYCALL "MaxRetries:2\n"; print MYCALL "RetryTime:60\n"; print MYCALL "WaitT...

...ar=chr($AGI->wait_for_digit('600')); print STDERR "input form rec char : $char\n"; if($char eq "*") { print STDERR "Dialing your number\n"; $srcfile="/tmp/mycall"; $dstfile="/var/spool/asterisk/outgoing/mycall"; open(MYCALL,">$srcfile") || die "Cant't open file :$srcfile $!\n"; print MYCALL "Channel:IAX2/bali:bali\@nain/25\@atif\n"; print MYCALL "MaxRetries:2\n"...

...uot;$stripcmd" != x ]; then $doit $stripcmd $dst; else true ; fi && + if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dst; else true ; fi +else + +# If we're going to rename the final executable, determine the name now. + + if [ x"$transformarg" = x ] + then + dstfile=`basename $dst` + else + dstfile=`basename $dst $transformbasename | + sed $transformarg`$transformbasename + fi + +# don't allow the sed command to completely eliminate the filename + + if [ x"$dstfile" = x ] + then + dstfile=`basename $dst` + else + true + fi + +# Make a temp...

hello everyone, thanks to todd 1.2.21 is out :) every release getting better, i would like to get consensus on these "important" bugs: #252078 logtail: should depend on perl >= 5.8 sarge as any other modern linux distro use perl 5.8.x, it's even inside of its base. backports are under the peril of its author if no one voices up, i'll close that bug in the next days.

...tive module at that time files found to be proper. rsync is completing successful without giving any errors. On comparing both files I see a big hole in standby file filled with 0's. Below is my rsync command - rsync -a -c -v --delete --timeout=250 --contimeout=30 --temp-dir=xxxx srcfile dstfile rsync is running in daemon mode. OS - QNX rsync version - 3.0.9 On trying to sync same files again sync happened properly. Does anybody have similar kind of issues? Please help me in this regard. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.sam...

...tftpClientSock > > > > NOT 09:28:49.324525 SECD: ctlRequestFile: Request > > > CTLSEP0019E7D16CD6.tlv > > > > NOT 09:28:49.327942 tftpClient: tftp request rcv'd from > > > > /usr/tmp/ctlSock, > > > > srcFile = CTLSEP0019E7D16CD6.tlv, dstFile = /usr/tmp/ CTLFile.tlv > > > > NOT 09:28:49.331598 tftpClient: auth server - tftpList[0] = > > > 10.10.10.10 > > > > NOT 09:28:49.332439 tftpClient: look up server - 0 > > > > WRN 09:28:49.335498 SECD: WARN:lookupCTL: CTL update in progress, no...

When I do rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/dir3 machine:/dir1/dir2/dir3 I get /dir1/dir2/Backup/dir3/... /Backup/dir3/dir4/... i.e. the tree under 'dir3' (my source tree) gets created under .../Backup. This is fine. But when I do the same thing with a single file like rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/file

...@@ -2396,9 +2406,12 @@ Converter::handleSTORE() > if (tgsi.getDst(0).isIndirect(0)) > st->setIndirect(0, 1, fetchSrc(tgsi.getDst(0).getIndirect(0), 0, 0)); > } > - return; > + break; > + default: > + assert(!"Unsupported dstFile for STORE"); > } > > +/* Keep this around for now as reference when adding img support > getResourceCoords(off, r, 0); > src = off; > const int s = src.size(); > @@ -2446,6 +2459,7 @@ Converter::handleSTORE() > mkTex(OP_SUSTP, getResourceTarg...

I have legitimate ssh access to two remote machines. ssh directly from either machine to the other is blocked by firewalls which I cannot control. $ rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/ receiving file list ... done rsync: mkdir user@host2:/tmp: No such file or directory rsync error: error in file IO (code 11) at main.c(319) I would like this to copy host1:/tmp/dir into

...<< c))) continue; @@ -2396,9 +2406,12 @@ Converter::handleSTORE() if (tgsi.getDst(0).isIndirect(0)) st->setIndirect(0, 1, fetchSrc(tgsi.getDst(0).getIndirect(0), 0, 0)); } - return; + break; + default: + assert(!"Unsupported dstFile for STORE"); } +/* Keep this around for now as reference when adding img support getResourceCoords(off, r, 0); src = off; const int s = src.size(); @@ -2446,6 +2459,7 @@ Converter::handleSTORE() mkTex(OP_SUSTP, getResourceTarget(code, r), code->resources[r].slot, 0,...

...rter::handleSTORE() >> if (tgsi.getDst(0).isIndirect(0)) >> st->setIndirect(0, 1, fetchSrc(tgsi.getDst(0).getIndirect(0), 0, 0)); >> } >> - return; >> + break; >> + default: >> + assert(!"Unsupported dstFile for STORE"); >> } >> >> +/* Keep this around for now as reference when adding img support >> getResourceCoords(off, r, 0); >> src = off; >> const int s = src.size(); >> @@ -2446,6 +2459,7 @@ Converter::handleSTORE() >>...

Commit c3083c7082 ("nv50/ir: add support for BUFFER accesses") disabled / commented out some of the old resource handling code, but not all of it. Effectively all of it is dead already, if we ever enter the old code paths in handeLOAD / handleSTORE / handleATOM we will get an exception due to trying to access the now always zero-sized resources vector. Disable all the dead code.

tgsi_default_instruction_memory / tgsi_build_instruction_memory were returning uninitialized memory for tgsi_instruction_memory.Texture and tgsi_instruction_memory.Format. Note 0 means not set, and thus is a correct default initializer for these. Fixes: 3243b6fc97 ("tgsi: add Texture and Format to tgsi_instruction_memory") Cc: Nicolai Hähnle <nicolai.haehnle at amd.com>