similar to: sshd and file descriptors

I'm trying to set up a machine which will be running multiple instances of NSD to serve different sets of zones from different interfaces. What I'm running into is that I can't specify different PID files to refer to on the command line. Are there any shortcuts or do I need to go write a patch? Any other implications of multiple instances? --

This problem has persisted for as long as I've used rsync. When the --delete option is used, not all files are deleted from the target, even though said files are not present in the source. The particular cases that cause this are when the target has a directory with files, and the source is something else, at least a symlink (this is the case I have seen). I'm taking a guess to say that

I was under the impression that --include and --exclude worked by matching patterns in the order given, and whichever matched first, whether that was an include or exclude determined the action for that file. I have a big directory from which I am attempting to transfer selected files. I want all files where the first level directory is anything, the second level directory is "2005"

A while back, I asked if there had been any consideration in making rsync support direct ssl (as opposed to just ssh). I've been looking around for a secure way (e.g. encrypted, so passwords are never in the clear, and even content is obscured from sniffers) to allow a set of limited-trust users (limited-trust being defined as mostly customers, whom you trust with their own data, but not with

http://bugzilla.mindrot.org/show_bug.cgi?id=293 Summary: sshd 3.3p1 doesn't work on Slackware Product: Portable OpenSSH Version: -current Platform: ix86 URL: http://www.slynet.lu/ OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo:

My understanding of the man page description of --exclude vs. --include is that the list of these is kept in order, and file names are searched against these parameters in that order for the first that matches and that one makes the decision. It doesn't seem to be working exactly as expected. But there is a factor involved that's making it unclear, which is whether or not *'s should

I just noticed that there is an extra blank line in the output generated by rsync when the --dry-run (-n) flag is used. This seems to have started with 2.6.0. Is this desired? The reason why I'm asking is because I use scripts that parse the output from rsync and little modifications in verbosity can make or break things easily. Thanks, -- Alberto [ads@localhost bin]$ rsync-2.5.7

I just upgrade a file server from RH7.2 to RH8.0. Now, I am having a heck of a time trying to sync up more than 345GB of data. I keep getting "kernel: Out of Memory: Killed process 10101 (rsync)" in /var/log/message. Has anyone seen this problem before? Thanks! Randy

Hi; I just attempted to install openssh-3.3p1 on a Sparc box running linux kernel 2.2.14-5.0 However any attempt to connect to the daemon causes a crash. (See below) Given the current security issue, will there be an available option for running the up coming 3.4 release on a Linux 2.2 kernel? Bob ><> ><> ><> ><> ><> ><>

http://www.eviladmin.org/~mouring/openssh.tar.gz If there are any issues that are not marked as known. Let us know ASAP. - Ben

Does anybody care about supporting non-English message locales in rsync? (Do all sysadmins speak English? :-) Would anybody contribute translations if we had the framework? -- Martin

I think someone posted this before, but I can't find it in the archives. I am using rsync to pull down source files to be compiled. The delete options are used to clear out any old files left over from previous. Normally this works. I've run into one case where it persistently fails. Within the directory created during compiling is a symlink to another directory, also created during

Hi Phil, answer to your questions: > Which specific Slackware? Too embarrassed to say? Really, really don't know exactly. :) Installed approx. 5 yeras ago (maybe 4.5, 4.6, maybe 5.0 ... who knows now ... ) > Which OpenSSL? 0.9.6a? 0.9.6b? 0.9.6c? 0.9.6d? Only info I found is 0.9.6. Let's suppose it's 0.9.6. ;) > How about telling me how long you're going

Hello openssh-unix-dev, Some time ago I successfully compiled version 3.1 of OpenSSH. Today I tried new OpenSSH version and I am not able to compile it. Configuration script runned well. When running make, following error occured: make[1]: Entering directory `/tools/openssh-3.4p1/openbsd-compat' make[1]: Nothing to be done for `all'. make[1]: Leaving directory

Hi, i try to learn how rsync lock files for create a backup, but.. not find any on www. some can help me and give any HOWTO or FAQ or document ? Thanks! -------------- next part -------------- HTML attachment scrubbed and removed

I was planning to use rsync to backup to a second drive, but I ran out of swap space. No problem, I will let rsync do it a few directories at a time overnight when the computer usually sits idle except for incomming email. I have 2 question: 1. How much memory does each file to be copied need. Obvisiouly I have too many files. 2. Why does this command work: rsync -ax /usr/xx /backup/usr/

Hi, 1. "make install-strip" (in rsync-2.5.x) tries to strip the manpages and thus fails; attached is a patch fixing the Makefile logic (and also adding DESTDIR -- convenient for package-building or test-installing). 2. I just fetched rsync-2.5.2 but the build (on i686-linux) badly fails. The complete log from configure and make is attached. regards Peter Breitenlohner

It guess I still haven't figured out the entire sematics of the --include and --exclude options. From reading the man page, it seems to say that what happens is that each file being checked is tested against each pattern in order, and when one matches the tests end, and whether it is --include or --exclude determines if that file is included or excluded. So I have on my server a big file

If I understand privsep correctly, and I'm not sure I do as there are some ambiguities in the illustration of what processes are doing what, there is a way to avoid doing fd passing. What I see is that fd passing is done to send the PTY to the user privileged process after the monitor process was requested to set one up. Why not go ahead and have the monitor set one up before it forks the

Hi all, after upgrading xapian I encountered the same problem as described in ticket #645 Read block errors after reopen() in our setup its 100% reproducible after each reopen(). I downgraded again and it seems the problem occurs in Version 1.2.16 and above. in <=1.2.15 everything works fine without seeing this error once. attaches strace shows read ends on FD. strace starts at reopen()