similar to: Settings file times only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have an iMac v10.6. I'd like to get it to connect to an old os/2 server, v4.5 fp3. Using smbutils on the iMac: $ smbutil -v view //sma-server1.sma.com smbutil: server connection failed: RPC struct is bad Can anyone suggest what changes may be made that will correct this error? Is it even possible? - -- James Moe moe dot james at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, linux 2.6.34.7-0.7-desktop x86_64 smbclient 3.5.4-5.1.2-2426-SUSE-SL11.3 I issue this command: smbclient -L SMA-STN14L -U jmoe I get: Connection to SMA-STN14L failed (Error NT_STATUS_BAD_NETWORK_NAME) In <smb.conf> [globals] section: workgroup = SOHNEN-MOE netbios name = SMA-STN14L Adding the -I option made no difference.

Trying to automate backup of the following local mounts/directories to a usb drive (/mnt/usbbackup); here's what's in my include file: + /home/gravyface/www/* + /mnt/datadisk1/music/* + /mnt/datadisk2/projects/* If I run the following, nothing happens, so I checked the man and I'm not specifying a source (I thought the include-from was the source): sudo rsync --progress -avz

On 09/13/2018 07:54 PM, Darren Tucker wrote: > I'd guess that the reason it doesn't work is that the key is encrypted > and neither the agent nor a tty to ask for the decryption passphrase > is available. Try repeating your command line test after unsetting > SSH_AUTH_SOCK > Okay. That reproduced the issue. Is there a recommended way to provide the decryption

sftp OpenSSH_7.6p1, OpenSSL 1.1.0h-fips 27 Mar 2018 linux 4.12.14-lp150.12.16-default x86_64 I created bash script to download database files once a week. It uses sftp as the agent. The script runs correctly when started from a command line. It fails when run from cron. Authentication with the remote server is set to use a private/public key and does not require an explicit password. Why

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, opensuse 13.2 linux v3.16.7-7-desktop x86_64 rsync v3.1.1 I used rsync to copy /usr/ to another volume with these options: - --recursive --one-file-system --links --stats --itemize-changes - --quiet --delete --times After I had modified the system to use the new /usr volume, I realized I should have added: - --perms --owner --group

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have been using rsync to backup our primary data stores. It works fine. Here are the options I use for doing that: rsync --recursive --links --times --dirs --stats --delete \ --itemize-changes --quiet --exclude-from=exclude-filename \ /data-store1/ /data-store2/ Recently I have had the need to actually synchronize the files between

rsync v3.1.0 linux v4.4.104-39-default x86_64 Found in the system log: 2018-02-22T05:02:00-0700 sma-server3 python3[31371]: backintime (sma-user3x/3): WARNING: Command "rsync -rtDHh --links --no-p --no-g --no-o --info=progress2 --no-i-r --delete --delete-excluded -i --dry-run --out-format="BACKINTIME: %i %n%L" --chmod=Du+wx --exclude="/bkp/cgate-backintime"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Local rsync version 3.0.7 protocol version 30. The remote rsync version is 3.0.5, I think. opensuse v11.3 linux 2.6.34.8-0.2-desktop x86_64 The nightly rsync run is getting this error: 2011/07/20 02:04:29 [17840] FATAL I/O ERROR: dying to avoid a \ --delete-during issue with a pre-3.0.7 receiver The options are: - --archive

I have a local directory that I am trying to sync with a remote directory. That's fine, but there's a lot of data that is out of sync so I decided to make a local copy of the difference to then bring to the remote location. So I ran a dry-run between the two to generate a list of files in listOfFiles.txt Then I ran rsync from local to localBackup. rsync -av

On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote: > --timeout is about network connection timeouts. You aren't using the > network so it doesn't apply at all. Even if you were networking an > unmounted filesystem is an empty directory as far as rsync is > concerned > and rsync would treat it that way with no idea that you intended to > have > something

Running rsync 3.0.6 on OS X 10.5.7 (on a MacBook Pro) and using the -b flag (and -v --verbose), the "backup_dir" is reported in the output, but sometimes on STDOUT and sometimes somewhere else. Note that the rsync daemon running on the "server" is 2.6.9 (on another MacBook Pro, OS X 10.5.7) For example, in bash, this happens: axe-MBP:bin work$ /usr/local/bin/rsync

http://dovecot.org/test/ - Added pop3_mails_keep_recent setting. Currently this only means that mails won't be moved from new/ to cur/ in maildir. More I/O friendly. - Fixed \Recent-flag handling and counters to work correctly with maildir. I think it's finally working right :) - mbox syncing fixes (but expunging still not implemented) - some other fixes.. Please try and report what

Dear All, I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options. This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created. -aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup

I have a script that runs nightly as a cronjob to backup my drive to a USB drive https://pastebin.com/yivqrGUC On the command line I use the --timeout option. Is this sufficient to ensure that if the external drive somehow becomes unmounted that rsync will gracefully fail without trying to write to the hard drive instead of the USB drive? rsync -vaWSHpl --timeout=15 --delete-excluded --filter

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20030728/49616c2f/attachment.bin

https://bugs.freedesktop.org/show_bug.cgi?id=69827 Priority: medium Bug ID: 69827 Assignee: nouveau at lists.freedesktop.org Summary: Uneven, jerky mouse movement, increasing CPU usage QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jimoe at

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear list members, there are two new rsync-features I made up and would like to discuss with you. If you think these new features might be useful for the whole rsync-community, please give me a note and I'll send you the patches (or post them here). 1.) Setting owner and/or group of backup files. In our servers I'm using rsync to backup

I am having a problem using the backup_dir option of rsync. The command being used is basically rsync --archive --delete --backup --backup_dir=PathToBackup/save user@fromsystem:FilePath/ PathToBackup/ The feature that is unique to this problem is that the "save" directory is under the path where the files are being backed up. Fortunately, rsync is clever enough to not delete