search for: replet

Just a tag-on for the thread about list posting etiquette, etc., etc. The following is a link to an excellent (if wordy) how-to-do-it-right instruction manaual replete with links to other treatises on the topic. The entire text of this document is emailed to the mailing list on the 1st of each month. This is the Cadillac of etiquette manuals. http://www.linux-sxs.org/index2.html Enjoy, -- Collins Richey If you fill your heart with regrets of yesterday and...

...gt; that defines the semantics of relevant hooks >> and then statically linking their compiled library with the >> program-under-test. >> >> At first glance, this brute-force method of inserting hooks at every >> salient location in the program-under-test seems to be replete with >> overheads. CSI overcomes these overheads through the use of >> link-time-optimization (LTO), which is now readily available in most >> major compilers, including GCC and LLVM. Using LTO, instrumentation >> hooks that are not used by a particular tool can be el...

Hi All, I''ve installed puppet and puppetmaster on 2 separate Virtual Machines. I''ve started the puppetmasterd in Verbose debugging mode and im guetting this error on the master when I try and connect to it with the puppet client... err: Could not find puppetc.myhost.com with names puppetc.myhost.com, puppetc It seams that I''ve setup the certificate right

...uch space is wasted by some of the default installations on CentOS. I think this was a 5.x box. Anyway, in /usr/lib/64 (and probably /usr/lib on non-64 systems), there were a lot of directories which have no bearing on a basic server. I saw firefox, openoffice and many, many other directories -- replete with enough files to seriously affect backup space over time. Does anyone have an available script or list of commands for removing most or all of these "generally unused" directories, packages or whatever they are? I found something a while back for shutting off unused services, but t...

...erence to keep.source() and keep.source.pkgs(), which I conjectured just ***might*** possibly be the ``obvious'' resource to which Prof. Ripley thought I ought to have resorted. However, after substantial experimentation, I am still at a loss to get at the original source code for arima() (replete with comments) save by accessing the original, ``unmade'' source for R. Not too hard, but not exactly ``immediate''. In the course of experimenting with keep.source.pkgs() I encountered behaviour which I found mysterious and which I'd like to understand better. Also if there...

...th this command: git fetch --tags Then you can compare the tagged releases like any other commit: git diff 0.23.1 0.23.2 I''ve also updated the PuppetSource wiki page with this info. -- Barondes'' First Law: Science abhors contradictions; scientists'' minds are replete with them. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com

...e remote server. However, we really need to fix this systematically, so this kind of problem doesn''t keep cropping up. Any ideas? 1 -http://reductivelabs.com/trac/puppet/ticket/594 -- Barondes'' First Law: Science abhors contradictions; scientists'' minds are replete with them. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com

...ram-under-test simply by first writing a library that defines the semantics of relevant hooks and then statically linking their compiled library with the program-under-test. At first glance, this brute-force method of inserting hooks at every salient location in the program-under-test seems to be replete with overheads. CSI overcomes these overheads through the use of link-time-optimization (LTO), which is now readily available in most major compilers, including GCC and LLVM. Using LTO, instrumentation hooks that are not used by a particular tool can be elided, allowing the overheads of these ho...

...the >> semantics of relevant hooks >> >> and then statically linking their compiled library with the >> program-under-test. >> >> At first glance, this brute-force method of inserting hooks at every >> salient location in the program-under-test seems to be replete with >> overheads. CSI overcomes these overheads through the use of >> link-time-optimization (LTO), which is now readily available in most major >> compilers, including GCC and LLVM. Using LTO, instrumentation hooks that >> are not used by a particular tool can be elided...

Hello all, Although i'm aware that version 1.0.15 is rather old, that's what is used in Lenny, so... Either way, the setup is rather simple, regular dovecot install, with maildirs residing on a "local" ext3 filesystem accessed through FC to a SAN (2Gbps link). The server has 2 cores (with HT), so "almost" 4 cores and 3GB of ram. A couple weeks ago we had a major

...if not impossible, to recover. It's also much more work than a direct translation to SPIR-V, so you will be investing extra engineering effort in order to generate worse SPIR-V. > So as a proposal, could I suggest the following next steps? > 1) Add a dummy SPIR-V target machine to llvm, replete with target triple > 2) Implement an experimental backend making use of globalisel to target SPIR-V code generation > 3) Add tests to verify correct execution > > Moving forward, the plan would be to develop this into a fully featured and complete backend, with a complete set of tests...

...st writing a library that defines the > semantics of relevant hooks > and then statically linking their compiled library with the > program-under-test. > > At first glance, this brute-force method of inserting hooks at every > salient location in the program-under-test seems to be replete with > overheads. CSI overcomes these overheads through the use of > link-time-optimization (LTO), which is now readily available in most major > compilers, including GCC and LLVM. Using LTO, instrumentation hooks that > are not used by a particular tool can be elided, allowing the o...

...lso much more work than a direct translation to >> SPIR-V, so you will be investing extra engineering effort in order to generate >> worse SPIR-V. >> >>> So as a proposal, could I suggest the following next steps? >>> 1) Add a dummy SPIR-V target machine to llvm, replete with target >>> triple >>> 2) Implement an experimental backend making use of globalisel to >>> target SPIR-V code generation >>> 3) Add tests to verify correct execution >>> >>> Moving forward, the plan would be to develop this into a fully fe...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''m trying to figure out why exec{} which subscribes to a file, doesn''t get triggered when the file is touched by puppet. I''ve got the following: exec { "/usr/sbin/postmap /etc/postfix/checks/access": refreshonly => true, subscribe => File["/etc/postfix/checks/access"];

...of relevant hooks >>> >>> and then statically linking their compiled library with the >>> program-under-test. >>> >>> At first glance, this brute-force method of inserting hooks at every >>> salient location in the program-under-test seems to be replete with >>> overheads. CSI overcomes these overheads through the use of >>> link-time-optimization (LTO), which is now readily available in most major >>> compilers, including GCC and LLVM. Using LTO, instrumentation hooks that >>> are not used by a particular to...

...t defines the >> semantics of relevant hooks >> and then statically linking their compiled library with the >> program-under-test. >> >> At first glance, this brute-force method of inserting hooks at every >> salient location in the program-under-test seems to be replete with >> overheads. CSI overcomes these overheads through the use of >> link-time-optimization (LTO), which is now readily available in most major >> compilers, including GCC and LLVM. Using LTO, instrumentation hooks that >> are not used by a particular tool can be elided...

Hi, In our dev/int environemnts, our user base wants to be able to change managed files at will during the day but be notified via email of changes that happen. At night they want the files replaced to their known good state if there were changed. I tried to do this with a custom function that wraps two file types, one that just watches checksum, the other that does a reset of content with a

...a direct translation to >>>> SPIR-V, so you will be investing extra engineering effort in order to generate >>>> worse SPIR-V. >>>>> So as a proposal, could I suggest the following next steps? >>>>> 1) Add a dummy SPIR-V target machine to llvm, replete with target >>>>> triple >>>>> 2) Implement an experimental backend making use of globalisel to >>>>> target SPIR-V code generation >>>>> 3) Add tests to verify correct execution >>>>> Moving forward, the plan would be to d...

...vant hooks >>>> and then statically linking their compiled library with the >>>> program-under-test. >>>> >>>> At first glance, this brute-force method of inserting hooks at every >>>> salient location in the program-under-test seems to be replete with >>>> overheads. CSI overcomes these overheads through the use of >>>> link-time-optimization (LTO), which is now readily available in most major >>>> compilers, including GCC and LLVM. Using LTO, instrumentation hooks that >>>> are not used by...

...then statically linking their compiled library with the >>>>>> program-under-test. >>>>>> >>>>>> At first glance, this brute-force method of inserting hooks at every >>>>>> salient location in the program-under-test seems to be replete with >>>>>> overheads. CSI overcomes these overheads through the use of >>>>>> link-time-optimization (LTO), which is now readily available in most major >>>>>> compilers, including GCC and LLVM. Using LTO, instrumentation hooks that >>...