similar to: Per-directory .cvsignore too aggressive

Displaying 20 results from an estimated 3000 matches similar to: "Per-directory .cvsignore too aggressive"

2002 Jul 25
1
OpenSSH 3.4p1's top level .cvsignore file
anyone who can help me understand- one of my developers reimported openssh snapshot from 0722 into cvs. he sent me the following email about an error he believes is in the snapshot i'm not a cvs-knowledgeable person, so i'm not all that clear on this, but should *.in files be in .cvsignore? i tried checking a later snapshot, but 0722 seems to be the latest one. .cvsignore is dated jun
2001 Apr 30
2
Add a couple .cvsignore files?
It would be nice if the CVS source had a .cvsignore file in the main dir with the following items: ssh scp sshd ssh-add ssh-keygen ssh-keyscan ssh-agent sftp-server sftp configure config.h.in config.h config.status Makefile ssh_prng_cmds *.out Plus a .cvsignore file in openbsd-compat that ignored "Makefile". ..wayne..
2002 Sep 17
0
Bug Report rsync 2.5.5 --delete and soft links to parent directories causes MAXSYMLINKS error
I have found an unwanted feature of rsync 2.5.5. It has to do with soft links and the --delete option in archive mode. The following shows how to reproduce the error. Provide a soft link that refers to a parent directory. %> /bin/ls -lR /tmp/src /tmp/src: total 16 16 drwxrwxr-x 2 wke sys_admin 239 Sep 17 16:18 dir1/ /tmp/src/dir1: total 32 16 lrwxrwxrwx 1 wke
2007 Dec 28
1
Odd behavior with --detect-renamed
Hello, I'm totally new to this list, so I hope I don't break all the rules. :) I've looked through the archives (and google), and I really can't find the answer to my question. I'm trying out the 'detect-renamed'-patch, and I've encountered some odd behavior. I've applied the patch to both rsync-2.6.9 and rsync-3.0.0pre7, and it's the same behavior.
2007 Nov 19
1
rsync-ing from two locations with same filenames (at different versions)
Hello, I would like to have a full repository, say, holding files full/a.txt (version 1) full/b.txt (version 1) full/c.txt (version 1) and a repository of updates, for example new/b.txt (version 2 - newer) Then, I would like to call rsync [flags] new/ full/ destination to get destination/a.txt (v.1) destination/b.txt (v.2) destination/c.txt (v.1) This simple case works
2004 Aug 06
1
.cvsignore
Hi: Just did my first svn checkout. Pretty painless. I noticed that icecast and each of its dependent modules (except m4) has a .cvsignore file. Am I right in thinking these are redundant now? Geoff. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to
2003 Feb 25
2
Difference in behaviour with --backup
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
2005 Sep 16
1
Bug#314473: rsync still fails badly with an "!" in .cvsignore
Here a bug report about "!" not working properly in 2.6.4 and above, paraphrased... > Ok, see attachment. I've tested it right now between two hosts > running rsync 2.6.3-2 and 2.6.6-1. It works in the forward direction, > backwards it gives > > '!' rule has trailing characters: ! > rsync error: syntax or usage error (code 1) at
2008 Sep 09
3
directories not correctly recognized rsync-3.0.4
Hi, I'm running rsync-3.0.4 on my UNIX system. I've just updated from rsync-2.6.9. I'm facing a general problem with the execution of files during a transfer process. The situation: 2 Directories (dir1 and dir2) on one machine with a some files in dir1 which shall be translated to dir2. rsync does not correctly recognize dir1 and dir2 as directories. It tries to transfer dir1 as a
2008 Oct 13
1
rsync hangs during --remove-source-files
Hi, I'm using the following command to move files from a to b: rsync -avvvv --remove-source-files --ignore-existing /path/to/dir1/ /path/to/dir2 >> logfile dir2 isn't empty so I only move files from dir1 to dir2 that don't exist already. Every so often rsync stops in the middle and doesn't continue with the result that I have to kill it. The last time it happened, rsync had
2000 Apr 03
1
2.0.7pre3: smbclient issues
My systems: rh61, 2.2.14 + smbfs-nls.patch. I refer to 2.0.7pre3 as 2.0.7 === 1) "ls" of an empty dir 1a) 1.9.18 doing "ls" to an empty samba dir: smb: \> ls 49550 blocks of size 16384. 33754 blocks available 1b) 2.0.7 doing "ls" to an empty samba dir: smb: \> ls ERRDOS - ERRbadfile (File not found.) listing \* <=======
2010 May 19
1
permission issues between 3.4.0 & 3.0.3?
Hi all!! I'm experimenting a set of problems when trying to connect Samba client to windows. I don't have admin rights on the windows side, so I should trust all my winSA admin is telling me. Windows side (server): In the server Side (win2k3), the SA defined a shared resource. The share-permissions tab the "domain users" group has typical permissions, and in the security
2004 Mar 17
0
Mask problems
Guys, I'm bumping into some stupid problem, really need some fresh ideas. Samba version samba-client-2.2.7-3.7.2 samba-2.2.7-3.7.2 samba-swat-2.2.7-3.7.2 samba-common-2.2.7-3.7.2 The goal is to upload all *.gz files only from dir* dirs. I do mask *.gz recurse mput dir* See the detailed output below But mput keeps grabbing non *.gz files ignoring the mask *.gz command. Am I doing
2004 Mar 19
0
Please, help with mput/mask!!! Thanks!
Guys, I really need some help. Samba version samba-client-2.2.7-3.7.2 samba-2.2.7-3.7.2 samba-swat-2.2.7-3.7.2 samba-common-2.2.7-3.7.2 I'm trying to upload all *.gz files only from dir* dirs. I do mask *.gz recurse mput dir* See the detailed output below But mput keeps grabbing non *.gz files IGNORING the mask *.gz command. Am I doing something stupid here? Thanks, Ruslan. [root at
2011 Mar 15
4
tar exclude question
Hi List, hope this is not too offtopic, but this bothers me and my backup. My backups are tar jobs in cron, eg: 20 23 * * * tar -zcf /mnt/backupInternalHosts/backup/backup.tar.gz /etc /root /home && touch /tmp/state_backup-backup This always sends me an unwanted email with: tar: Removing leading `/' from member names I consider this a bug because this informal message is
2007 Dec 09
3
OT: Rsync question
Hello All, I have an off topic question about rsync and was wondering if i can get some kind person help with it. I have two servers with each server have three same directories on them /dir1/ /dir2/ /dir3/ . How would i achieve this by using rsync? I have tried rsync -avrt --delete server_ip:/dir1/ /dir2/ /dir3/ /dir1/ /dir2/ /dir3/ this does not do anything except give errors. Someone on IRC
2018 May 17
0
New 3.12.7 possible split-brain on replica 3
Hi mabi, Some questions: -Did you by any chance change the cluster.quorum-type option from the default values? -Is filename.shareKey supposed to be any empty file? Looks like the file was fallocated with the keep-size option but never written to. (On the 2 data bricks, stat output shows Size =0, but non zero Blocks and yet a 'regular empty file'). -Do you have some sort of a
2006 Apr 25
1
deletion those files from destination directory, that no longer exist in source directory.
Hallo I thought that I need to use `--delete' option for that, but it looks like not. Problem explanation: prompt# ls /tmp/dir1/ /tmp/dir2/ /tmp/dir1/: fil1.txt /tmp/dir2/: fil1.txt fil2.txt prompt# rsync --delete /tmp/dir1/* /tmp/dir2/ prompt# ls /tmp/dir1/ /tmp/dir2/ /tmp/dir1/: fil1.txt /tmp/dir2/: fil1.txt fil2.txt # fil2.txt still exists My question is,
2010 May 05
2
[Bug 1767] New: Inconsistend wildcard expansion in 'ls *'
https://bugzilla.mindrot.org/show_bug.cgi?id=1767 Summary: Inconsistend wildcard expansion in 'ls *' Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sftp AssignedTo: unassigned-bugs at mindrot.org
2004 Feb 06
3
Please help : Strange 'file has vanished' behaviour with rsync on windows.
Please help : Strange 'file has vanished' behaviour with rsync on windows. I need to run rsync on windows and sync shares thru UNC names. When I try : rsync -e ssh -av //mypc1/myshare1/dir1/* //mypc1/myshare1/dir2/. rsync does a copy but says "file has vanished" for every file. Then when I run: rsync -e ssh -av --dry-run //mypc1/myshare1/dir1/* //mypc1/myshare1/dir2/. it shows