similar to: FW: Rsync 2.5.6 ssh-basic.test patch

Dear list, I'm relatively new to using ssh. I'm trying to use the -R option to set up a forwarded port between two machines. Specifically I'd like to be able to ssh to machineB from machineA and then have a port on machineB that I can connect to machineA with. If my understanding is correct I'd need a command like: machineA> ssh -R 10000:machineA:23 machineB This should

I'm probably doing something I'm not supposed to even try, but I'm trying for "proof of concept" before physically setting up a distant network because of logistical issues. Anyway, I have tincd running as a service on two windows machines on the same lan. I'm trying to establish a connection between those two computers on the vpn ip's (10.20.30.1 and 10.20.40.1).

I am not sure where to begin so I will be as verbose as I can to explain the problem. I have 3 servers. Their specs are: Machine A: Redhat 7.1 kernel 2.4.9-34 openssh 3.1p1-5 Machine B: Redhat 7.3 kernel 2.4.9-31 openssh 3.1p1-5 Machine C: Debian Woody kernel 2.4.18-bf2.4 openssh 3.4p1 rsync 2.5.6 I am running an rsync over ssh from Machine C to Machine B with the following: rsync --verbose

I had a quick look for an answer to what I'd presume is a common Q but failed so wondering if somebody here would point me in the right direction, please & thanks?! I wish to use rsync to backup users' home dirs from machineA (Debian) to machineB (Fedora). I have a script, say backup.sh, in my own home dir and linked to from /etc/cron.daily and have set up the ssh keys so

Hi, I have a smb pdc running which works quite well so far, and would like to know if this feature is possible. I have two locations, and I want all users to authenticate on Machine A. Howver there are some users that are closer to machine B, and I would like to be able to have the homes of those users on machine B rather than machine A (they should authenticate on machine A anyway). Is this

Rsync folks: I couldn't get the ssh tests to work in rsync 2.5.6 and it doesn't appear that they ever could have worked. There were two problems with the script I noticed: 1) The "from" directory is never populated with files to test. It looked like the "hands_setup" function from rsync.fns was designed for this, so I added it in. 2) The "F1" variable

I have searched for this and the solutions I found were for instances where the workgroup name *was* too long. However, my workgroup name is *not* too long. The spaces between PEGASUS and ^[ are part of the message, I did not add them. If you count them there are 16 total including ending ^[. I can't figure out where the spaces are coming from. This is the same for every Samba

Has anyone used Agent Forwarding in 3.4p1? We can't seem to get it working under Solaris 2.6 or 8 (Sparc).

I'm using the very latest 'version 3.0.1pre3 protocol version 30', on both ends, and have seen a date/time discrepancy in the log on the receiver. The sending machine (machineA) is in US CDT while the receiver is in US PDT. Both sender and receiver have their time set correctly. a contiguous snippet from the log on the receiver : (note the first three timestamps are correct:)

Hello, I wanted to fit a linear mixed model to a data that is similar in terms of design to the 'Machines' data in 'nlme' package except that each worker (with triplicates) only operates one machine. I created a subset of observations from 'Machines' data such that it looks the same as the data I wanted to fit the model with (see code below). I fitted a model in

Presently, the Samba documentation says that the default NetBIOS username used by client-type applications is determined by the following (from smbclient(1)), If no username is supplied, it will default to an uppercase version of the environment variable USER or LOGNAME in that order. If no username is sup- plied and neither

>> From: Reindl Harald <h.reindl at thelounge.net> >> To: samba at lists.samba.org >> Date: 02/25/2015 02:52 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >> >> >> Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >>>> I have searched for this and the solutions I found were

Perhaps a stupid question, but i will give it a try: I have two machines on libvirtd session and network on usermod. Can i (somehow) cross these two machines ? machineA: ip addr add 10.10.10.101/24 dev eth0 ip route add default via 10.10.10.102 dev eth0 machineB: ip addr add 10.10.10.102/24 dev eth0 ip route add default via 10.10.10.101 dev eth0 -- Evaggelos Balaskas - Unix System Engineer

My question concerns the logic behind hypothesis tests for fixed-effect terms in models fitted with lme. Suppose the levels of Subj indicate a grouping structure (k subjects) and Trt is a two-level factor (two treatments) for which there are several (n) responses y from each treatment and subject combination. If one suspects a subject by treatment interaction, either of the following models seem

Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >> I have searched for this and the solutions I found were for instances >> where the workgroup name *was* too long. However, my workgroup name is >> *not* too long. The spaces between PEGASUS and ^[ are part of the >> message, I did not add them. If you count them there are 16 total >> including ending ^[. I

Executive summary: Why can I not have a private key which is `public' ? Gory details .... I'm new to openssh. I've been using ssh for years. However, I'm in the process of investigating RH 7.* (0.91 at the moment) and am wanting to be as `standard' as possible, so trying openssh. I looked on http://www.openssh.com/list.html but could not find a list for "general

Hello, Noticed a couple of problems with the rsync testsuite. I have included a possible patch for each problem (attached & inlined.) The first problem is that on OpenBSD when make test is run and tests are skipped you see messages like this: cat: "/tmp/rsync-2/rsync/testtmp.chown/whyskipped": No such file or directory SKIP chown () After my patch, you get the appropriate

>> From: schulz at adi.com (Thomas Schulz) >> To: durwin at mgtsciences.com, h.reindl at thelounge.net, > samba at lists.samba.org >> Date: 02/25/2015 06:39 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >>>> From: Reindl Harald <h.reindl at thelounge.net> >>>> To: samba at

Sviatoslav Sviridov [mailto:svd@ns1.lintec.minsk.by] wrote: >It would be good if attached patch will be included in upstream. This >patch adds option --apt-support for rsync and with this option rsync >will print some additional information about file being transfered. No >program logic changed. Having this option in rsync we can have apt with >rsync method support. 1. What is apt?

Ville Herva [mailto:vherva@niksula.hut.fi] wrote: > Of course, whether O_TEXT is defined or not does not > necessarily imply the availability of "t", but I > can't think of better alternative. Stratus VOS implements O_TEXT and O_BINARY but does not recognize "t". We have the options defined in ANS C and in POSIX. I'm at home and don't have my reference