search for: ipall

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

Under certain circumstances (repeatable with a workaround) the client in openssh-2.1.1p3 and p4 closes file descriptors and then calls select() with the stderr one in the write fd_set. The circumstances which cause this appears to be that the closing of stdin/stdout/stderr occurs before the last of the stderr data is written to stderr. This occurs when a tty is not allocated, but the error

When using the -z and -B65536 options together, sometimes there is file corruption. Client and server are both compiled against zlib 1.1.4, so the gzip corruption shouldn't be there, right? With -z and -B32768 there is an error, but it is detected in a different way. With -B65536 and without -z all seems to be going OK. With -B16384 and with -z all seems to be going OK. I'm guessing

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

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"

After doing a fresh extraction of the source for 2.6.0, I execute ./configure and it enters a loop with no output before or during. I let run 20 minutes just to see if it would ever do anything and it did nothing else. Host system has: Linux: 2.4.23 Slakcware: 9.0 bash: 2.05b.0 gcc: 3.2.2 glibc: 2.3.1 I have a big (huge) strace of it here:

Are there any version compatibilities between linux and klibc? I tried to compile the latest klibc (1.5.18) with the latest linux (2.6.32.15) and there is miserable compile failures. It looks like klibc wants some headers to be in include/asm (linked in my case to include/asm-x86) but they are instead in include/asm-generic (it seems all headers but one are in there). I put together this script

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

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 have an openssh RPM package that restarts the sshd server during an upgrade if the daemon is already running. So far, so good, restart works. But I observed the following behaviour: - when issuing rpm -Uvh bla.rpm, rpm, obviously, opens the rpm file and gets a file descriptor. Say, 8. - rpm does its stuff and spawns a shell to execute the %post script. The shell also gets fd 8 (should rpm

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

Last year I put together a script that did a combined kernel header export from a pristine kernel tarball, then a build of klibc from a pristine klibc tarball. One of the intentions for this was to be independent of the host kernel and its headers, so I could build klibc for other targets of the same architecture. I even did this for a wide range of klibc and kernel version combinations to see

Server host config: Slackware 8.0 (custom boot scripts) glibc-2.2.3 gcc-2.95.3 Linux-2.4.18 Client host config: (same as server) Symptom: session disconnects with no message to client: ============================================================================= phil at antares:/home/phil 153> ssh -V OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f phil at antares:/home/phil 154>

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

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

Is there a list of which kernel versions (are supposed to) work with (each version of) klibc? I do recall reading something that said klibc should run under any version of the kernel, regardless of which version it is compiled against. Following the new instructions on this list earlier (to use the KLIBCKERNELSRC= parameter to point to the installed kernel headers) as well as also making the

Is there a configure option to build OpenSSH mostly statically? I want to have openssl libraries statically linked. I'd prefer libc (and related) not be, and libz could go either way. -- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam at ipal.net | Texas, USA | http://phil.ipal.org/ |

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

[garbage in Chinese snipped] Is there any way to set up a post-confirmation system for non-subscribers so that their posts do not get distributed unless they confirm first? -- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam at ipal.net | Texas, USA | http://phil.ipal.org/ |