search for: delete_files

Hi All, I have an issue with the ODBC voicemail storage option with asterisk. All appears to work fine, however, I get several sql execute warnings. I was wondering if anyone out there could help me get to the bottom of what is causing this and how I could possibly go about rectifying it. The warning message we are getting is as follows: WARNING[30115]: app_voicemail.c:1280 delete_file: SQL

Regarding "rsync error code 23" could the below "delete_file: ...file exist" failures cause the error code 23? Or, how can I resolve this as these are the only errors I see in the log files. Thank you! START Tue Aug 26 11:10:12 PDT 2008 /home/filerep/bin/rsync -e /var/openssh/bin/ssh --archive --stats --timeout 3600 fmttcesrv1::tce_data

Hello list. I've got following: rsync: opendir "client05" (in Profili) failed: Permission denied (13) rsync: delete_file: rmdir(client02/SendTo) failed: Permission denied (13) Am I correct if I say that the "opendir" is related to the source I'm trying to rsync, but the "delete_file" is related to the destination? Flavio Boniforti PIRAMIDE INFORMATICA

[ I'm not subscribed to this list; please CC any followups to me as well ] When a user invokes "ssh-add" with no arguments, I think we should default to adding both version 1 and version 2 keys. Here's a patch against the source included with my Debian package of OpenSSH: walters at space-ghost:/usr/src/ssh/openssh-2.9p2$ diff -u ssh-add.c~ ssh-add.c --- ssh-add.c~ Thu Apr

The patch below does two things. 1. If invoked with no arguments, attempt to add both RSA and DSA keys. 2. Remember the last successful passphrase and attempt to use it on subsequent key files which are added. Note that the latter part of the patch extends the period of time during which the passphrase is held in clear text in the ssh-add process, but doesn't introduce any _new_

Hi, How do I disabled asterisk to use database and storage voicemail in directory. Im getting the below error [Dec 3 19:08:53] WARNING[4934]: app_voicemail.c:3430 inboxcount: Failed to obtain database object for 'asterisk'! [Dec 3 19:08:55] WARNING[5129]: app_voicemail.c:2353 last_message_index: Failed to obtain database object for 'asterisk'! [Dec 3 19:09:04]

I have what I believe to be a bug in the behavior of the current (2.6.4) version of rsync. While trying to upgrade from version 2.5.2 to the current version (for security concerns), I noticed the following difference in behavior between the two versions which is preventing the upgrade: If you have a directory tree on the target such as the following: dir/pdf/file1.pdf dir/pdf/file2.pdf

...p.c:266 266 if (!kept && preserve_hard_links && file->link_u.links (gdb) where #0 0x80536c0 in keep_backup (fname=0x808f060 "rsync.core") at backup.c:266 #1 0x80537c9 in make_backup (fname=0x808f060 "rsync.core") at backup.c:297 #2 0x804c003 in delete_files (flist=0x8096100) at receiver.c:112 #3 0x805028c in do_recv (f_in=3, f_out=3, flist=0x8096100, local_name=0x0) at main.c:434 #4 0x805093c in client_run (f_in=3, f_out=3, pid=-1, argc=1, argv=0x8095004) at main.c:666 (gdb) p *file $1 = {modtime = 1076386251, length = 577536, mode = 33152,...

https://bugzilla.samba.org/show_bug.cgi?id=12741 Bug ID: 12741 Summary: stop rsync on "No space left on device" Product: rsync Version: 3.1.2 Hardware: x86 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org

I'm trying to switch to using rsync for updating a huge software library containing binaries, text files, symlinks, and so on. We've been using something homegrown which I'm not that happy with - it's a perl script that systems cp and chmod and such. The problem I'm seeing is: target computer: directories ctime-5 and ctime-5b3 are distinct directories source computer:

...ete -avun --max-delete=1 src/ dest building file list ... done deleting 2 deleting 1 sent 81 bytes received 20 bytes 202.00 bytes/sec total size is 0 speedup is 0.00 It deletes 2 files while --max-delete=1 was specified. I think it has something to do with deletion_count in delete_files(receiver.c). Bye, Laurens

Hello, I'm backing up a file server using rsync from a cron job, which recently started to give me errors like: delete_file: rmdir "/some/path" failed: Directory not empty symlink "/some/path" -> "/some/other/path" failed: File exists Looking at the involved files and directories, it looks like the user decided to replace a directory with a symlink, but

Anyone here run rsync on a Win32 platform? I know, I'm a glutton for pain. Anyway, I'm using 'cwrsync' on one system to copy files from a local drive (F:) to a mapped (network) drive (Y:). The problem I'm having is with that infamous 'Network Trash Folder'. I can't get it to ignore it on the remote (mapped) drive, and it doesn't exist on the local drive.

I've gotten several different errors with rsync. Maybe someone can help me. 1. rsync -azSH --stats --delete-after /export/home remote:/export/home/bkup delete_file: rmdir(home/greg/vnmrsys) : File exists rsync: symlink "home/greg/vnmrsys" -> "/export/home/vnmrsys": File exists unexpected tag 91 rsync error: error in rsync protocol data stream (code 12) at io.c(298) 2.

Hi, sorry if this is old stuff, but I did my best to look first... Have been getting errors along these lines: mv mydir mdir.2002 ln -s mydir.2002 mydir Then update mirror with rsync -av --delete-after. Without --delete-after, no problem, with --delete-after, get a code 23. The attached shell script will recreate the error (on my machine, at any rate). Just run it from a clean directory.

Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.

Hi, sounds somehow stupid, but I can''t get rid of my files that I uploaded into my application via the file_column plugin. Any suggestions? Cheers Thomas -- Posted via http://www.ruby-forum.com/.

We've just been hit rather badly by a very nasty bug that can cause rsync to silently discard files or fill them with zeroes. It happens when e.g. opendir() succeeds but readdir() returns an error; rsync does not check for an error from readdir() and so simply ignores the error (along with any remaining files in the directory). No error is reported to the user, who will then happily

I've run into a bug in the IO handling when reading a file. Suppose I have a file that lives on an NFS filesystem. That filesystem is NOT being exported with auth=0 permissions. So, if I try to access a file as root, it successfully opens the file, but subsequent reads fail with EACCES. This produces a destination file full of null bytes. I noticed this with 2.5.7, but checked 2.6.2 as

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean