similar to: Connecting an iMac to os/2

-----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.

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

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"

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

Hello, samba v3.0.7 on suse linux v9.1 os/2 v4.x I have started the process of replacing our os/2 hosts with linux, starting with the server(s). Most of the problems have been firewall related, a topic only briefly discussed in the docs (nudge). Some of the hosts can now interact with the linux samba shares; not all though. I have run ip traces and have gotten to a point that is a

-----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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 I am backing up data to a USB memory drive that is formatted FAT32, which does not comprehend linux permissions. I added the "--no-perms" option to the option set. rsync still attempts to change the permissions. OPTS = "--no-perms --archive --stats --delete --itemize-changes - --quiet

-----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

-----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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 rsync v3.0.7 (also seen with 3.0.5) linux 2.6.34-12-desktop x86_64 os/2 v4.50 fp3 rsync makes an unusual error when building its file list for a transfer: it decided to move a directory further down the directory tree than where it was located in the source volume. Even more strange is that during the next run of rsync, it adjusts the *source*

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 rsync v.3.0.7 protocol version 30 opensuse v11.4 linux v2.6.37.6-0.20-desktop x86_64 rsync --recursive --links --dirs --stats --itemize-changes --quiet \ --size-only --exclude-from=/home/sma-user3x/bin/rsync-exclude.txt \ --delete --no-times --omit-dir-times \ /data01/t-drv/websites/ /t/websites/ The sub-directories /websites/site-logs/... are

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I restored a filesystem by using rsync to copy directories and files from a backup volume to the newly recreated volume. All of the re-created files were given the current date and time rather than the original file's timestamp. I am sure there was a way to prevent that from happening. Is there a way to use rsync to set the timestamps

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 linux 2.6.37.6-0.20-desktop x86_64 Below is a log of a backup session. I do not understand why the "exclude=/data01/..." is being ignored. The session is started in a bash script. The actual text is: - --exclude='/data01/t-drv/websites/owncloud/data/sma-admin/' I guess rsync cleaned it up to suit itself.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Normally, I would say that --checksum is actually slower than just letting rsync re-copy everything and therefore is almost always the wrong thing to do. However, in this case, you really don't want to overwrite the running OS even with files that are essentially the same. So, if the system is running from that storage then --checksum might

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, samba Version 3.5.4-5.1.2-2426-SUSE-SL11.3 We have recently transferred our file services from one host to another. The old host was an OS/2 server. OS/2 is basically a single user OS; the file (and directory) permissions were mostly irrelevant. The new server is linux OS, opensuse 11.3 distribution. It, of course, has more to say about

openSUSE v13.1 linux 3.11.10-11-desktop x86_64 samba 4.1.6 I recently upgraded an openSUSE server from v12.3 to v13.1. In the older version there was no problem about mounting a remote volume offered by an ancient OS/2 system. Now there is. Trying to mount it by command line: root:/home/sma-user3x> mount /t2 Retrying with upper case share name mount error(6): No such device or address

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No, even if bandwidth is your concern I would say that --checksum is wrong. Maybe if bandwidth is so scarse that a few KB vs a few MB equates to dollars then sure, use --checksum. Otherwise, letting rsync re-delta-xfer everything is certainly faster and not much more bandwidth intensive than --checksum. Plus that is only if you screwed up and ran

I've read everything I've found on tcpdump-smb, and still can't get it to work right. I downloaded the binary from samba.org, and executed the command like so: (The command belowis directly from the README.smb that comes with tcpdump-3.4a5.tar.gz) ./tcpdump -i eth0 port 139 host 192.168.0.1 tcpdump: parse error How do I use it to get the decoded smb output? BTW: I also

Hi all ! I have a little problem here mounting or browsing samba shares. I have a FreeBSD 4.6.2 running samba, and a share on that called public. when I try to mount that share it asks for password, and then gives an error: ex. libra# mount_smbfs //maxi@samba/public /mnt Password: mount_smbfs: can't get handle to requester (no /dev/nsmb* device) libra# I can list the shares with