similar to: Garbled mails in Maildir storage

Vladimir, I believe I've corrected this situation with version 1.299 of Makefile.rules. It now only uses find and install to do the installation of the header files. pax isn't used any more. Hopefully this helps you. Reid. On Wed, 2005-02-16 at 04:18, Vladimir Prus wrote: > Hello, > I've just tries make && make install on a fresh CVS tree, and get: > >

Hello, I'm having some routing issue with my tinc setup. I'm running a fairly basic VPN configuration between two networks: ------- Site A: ------- --- tinc-up --- #!/bin/sh /sbin/ifconfig tap0 hs ether fe:fd:00:00:00:00 /sbin/ifconfig tap0 10.11.1.2 netmask 255.0.0.0 /sbin/ifconfig tap0 -arp ---- tinc.conf --- Name = orca Hostnames = no InterfaceIP = 63.108.71.7 KeyExpire =

On Wed, 2005-02-16 at 04:18, Vladimir Prus wrote: > Hello, > I've just tries make && make install on a fresh CVS tree, and get: > > llvm[0]: Installing include files > /bin/sh: line 1: pax: command not found > This is a known issue. We plan to make the makefiles not depend on pax. > Two questions. > > 1. Why install process requires some nonstandard

Oh my god.... what is this? Getting this on first boot of new client. Aug 24 01:11:09 app03 puppet-agent[5392]: Reopening log files Aug 24 01:11:09 app03 puppet-agent[5392]: Could not request certificate: Neither PUB key nor PRIV key:: header too long I stop the client, and remove the ssl directory on the client: [root@app03 puppet]# service puppet stop Stopping puppet:

Hello, I've just tries make && make install on a fresh CVS tree, and get: llvm[0]: Installing include files /bin/sh: line 1: pax: command not found Two questions. 1. Why install process requires some nonstandard tool? Is it possible to get away without it. 2. autoconf/configure.ac has this: AC_PATH_PROG(PAX, [pax], [pax]) but Makefile.rules uses plain 'pax',

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:05.libarchive Security Advisory The FreeBSD Project Topic: Errors handling corrupt tar files in libarchive(3) Category: core Module: libarchive

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:05.libarchive Security Advisory The FreeBSD Project Topic: Errors handling corrupt tar files in libarchive(3) Category: core Module: libarchive

Apartamentos Lamy Algarve Arma??o de P?ra www.apartamentoslamy.com - Telefone 282 315 601 Aproveite as nossas promo??es. Fa?a uma pausa, viaje at? ao Algarve e desfrute de umas f?rias no conforto da Primavera. T1, s/Ac e pouca vista de mar, at? 30 de Maio de 2015. Special price until the 30th May 2015. One bedroom apartment without air conditioning and little sea view. 2 pax = 175? (7

I downloaded the latest version of puppet 2.6.0 today, and still can''t get parameterised classes to work. At least, I think it''s 2.6.0... the version number in the RPM spec file says 0.25.5. This simple example: /etc/puppet/manifests/nodes/pax/name01.pax.xxx.com.pp: node ''name01.pax.xxx.com'' { class { amodule::afunc: version => "1.0" } }

I am replacing my samba 4.1.9 with version 4.1.14. While tarring my /usr/local/samba in preparation for this I got a number of message about not being able to backup a socket. So I switched and used pax to create the tar archive. I got the same message in addition to the message about not backing up the socket I get messages like this: pax: ustar header field is too small for ./var/locks/sysvol/

On Sep 16, 2009, at 10:05 AM, Stefano Delli Ponti wrote: > Chris Lattner: >> Comparing -O3 (and even -O4) is interesting, but we want all >> optimization levels to perform better than GCC :). Lots of people >> use -O2 and -Os, so comparing against other compiler's -O2 and -Os >> levels is just as interesting as comparing -O3 vs -O3. > > My thinking

I've paraphrased the OS X installer developer's comments: there's a bug in Installer that is preventing the archive from working right. Below is the fix for the problem. First (obviously) run the installer. Since the executables are in the archive.pax.gz file in the installer package, first do a "show package contents" on the package file, then unstuff the enclosed

Hi, I''m trying to get PaX (http://pax.grsecurity.net) working on a 64-bit paravirt_ops guest under xen. One of the features that PaX uses under a 64-bit kernel is the NX bit. I''m using the paxtest utility (available at http://paxgrsecurity.net) to test whether the NX bit is working. On a host with NX support, a 64-bit 2.6.18 xen kernel has a working NX bit. Under a vanilla

On Mon, 25 Oct 2004, zhou feng wrote: > I have some questions about LLVM > 1. I recently compiled LLVM on my X86 machine correctly. But when I use > the built LLVm compiling programs(in the getting started guide), I got > an warning saying can not find library "lc" (something like that). Yet > LLVM did yeild a execution native code and it runs correctly except with > a

hi, all I have some questions about LLVM 1. I recently compiled LLVM on my X86 machine correctly. But when I use the built LLVm compiling programs(in the getting started guide), I got an warning saying can not find library "lc" (something like that). Yet LLVM did yeild a execution native code and it runs correctly except with a waring saying something like "__main**"(I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since you are in an environment with millions of files I highly recommend that you move to ZFS storage and use ZFS's subvolume snapshots instead of --link-dest. It is much more space efficient, rsync run time efficient, and the old backups can be deleted in seconds. Rsync doesn't have to understand anything about ZFS. You just rsync to the

Not to mention the fact that ZFS requires considerable hardware resources (CPU & memory) to perform well. It also requires you to learn a whole new terminology to wrap your head around it. It's certainly not a trivial swap to say the least... Thanks, -Clint On Mon, Apr 6, 2015 at 9:12 AM, Ken Chase <rsync-list-m829 at sizone.org> wrote: > This has been a consideration. But it

Folks, We faced a similar situation to that which Ken described - we recycle backup directories, for good reason. There is a patch to solve the problem. Our systems administrator provided the following description of the patches we use: ============================================================================ 1. rsync_link_dest improvement by Bryant Hansen Normally, existing files in

How do I debug errors with external nodes? When my client connects, the following appears on the puppetmaster when running in debug mode. It''s not feasible to always be running the pupeptmaster in debug mode. debug: importing ''/etc/puppet/modules/yum/manifests/client.pp'' in environment production info: Automatically imported yum::client from yum/client into production

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=GB2312" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Yes, I checked that envvar, and it is set.<br> The error msg when compiling a .c