search for: phma

...could I convert 2 factor variables in a single factor variable which is the combination of the other 2. Example: lith: a factor 2 levels "ca", "ma" sp: a factor with 2 levels, "ph", "qi" and I'd like to obtain: splith: a factor with 4 levels: phma, phca, qima, qica on way is by using ifelse: splith <- as.factor(ifelse(sp=="ph", ifelse(lith=="ma", "phma", "phca"), ifelse(lith=="ma", "qima", "qica"))) which works fine, but I've got the feeling that it can be done i...

Hi All I have compiled rsync on a Solaris 5.5.1 machine1 . I have compiled this on a partition on the machine as root. I have done the following shared the Partition on the machine i have compiled. mounted this partition this partition on the machine2 where I need to rsync data then When I issue the command on machine2 as rsync -avz machine2:/x machine3: It gives me sh :rsync not found EOF

...ithout a password, but I cannot get from A or B to C without a password. sshd_config is identical on A and C. My public key is in authorized_keys on C, and all files in .ssh and .ssh itself have mode 600 and 700 respectively. C is behind a port-forwarding firewall. Would that make any difference? phma

...get the list of modules over a secure connection ? > > Modules aren't used when you use rsync over ssh. You might try > forwarding port > 873 (the rsync port) over ssh from some unused local port and > using the --port > option to rsync to that port on localhost. > > phma >

Howdy, I am pretty "green" with rsync so any help will be much appreciated. I want to mirror webserver A and webserver B. The two directories I want to mirror are /www/home and /www/default. I was wondering how I would set this up in rsycd.conf and how I would call it in a script? Thanks David

I just finished installing rsync on one of my servers. But when I go to do a test connection via "rsync web1::" I get the following error rsync: failed to connect to web1: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(84)

Hello all, A few days ago I noticed that the following seems to happen when upgradign OpenSSH on Linux-based (/etc/rc.d/init.d/sshd) based systems: - sshd is restarted with 'sshd restart'; however sshd serving in port 22 is not replaced. - you have to kill the old one (netstat -ltp | grep :ssh ; kill ...) first, then restart sshd. - This might happen only when performing the upgrade