similar to: Re: [Logcheck-commits] CVS logcheck/src

On Sat, 15 May 2004, CVS User ttroxell wrote: > if [ -f /etc/logcheck/header.txt ] ; then > - $CAT /etc/logcheck/header.txt >> $TMPDIR/report > + $CAT /etc/logcheck/header.txt >> $TMPDIR/report \ > + || error "Could not append header to $TMPDIR/report Disk full?" > fi > } > > @@ -152,7 +157,8 @@ > # Add a footer

i did some cleanup first, but now i'm choking on a much earlier stage than i first thought. -- logcheck for file in $(egrep --text -v "(^#|^[[:space:]]*$)" $LOGFILES_LIST); do logoutput "$file" done -- that falls apart if you insert in /etc/logcheck/logcheck.logfiles a line like /var/log/auth .log even if you escape it with "", which is a valid

On Tue, 2005-05-03 at 07:20 +0000, CVS User maks-guest wrote: > Modified Files: > logcheck.sgml > Log Message: > > minor addition describe 3 layers. > remove the url tag not recognized by docbook2man. > + > + <para>The reported messages are sorted in three different layers. > + The system events verbosity is governed by aboves level choice. > + The

hello russel, On Mon, 10 Jun 2002, russell at coker.com.au wrote: .. > I would like to be able to have different parts of the report sent to > different people. For example if I install a new daemon on a server > I want the messages for that daemon going only to me (not the entire > admin team) until I get it working properly. Otherwise excessive > spurious messages lead

If I have a "simple" variable value, this works fine: capmon@peter:~> puppet -e ''$v="xyz" exec { f: command => "/bin/echo v is $v", logoutput => true }'' notice: /Stage[main]//Exec[f]/returns: v is xyz notice: /Stage[main]//Exec[f]/returns: executed successfully But how do I escape "bad" values of $v? Painful examples like the

I''m using puppet 0.25.1. I''ve got a simple resource: exec { "/bin/ls $oracle_base/dba/bin/database_backup.ksh": logoutput => on_failure, } and I don''t want it to log every time it''s successfully run: $ sudo tail -F /var/log/messages | grep puppetd Feb 17 16:36:11 test puppetd[26614]: (//my_module/Exec[/bin/ls /u01/

I'm running logcheck on a machine hosting a bunch of virtual machines using vserver, so I'd like to expand shell wildcards in the "logcheck.logfiles" file. So instead of entering /var/lib/vservers/v1/var/log/syslog /var/lib/vservers/v2/var/log/syslog /var/lib/vservers/v2/var/log/syslog I can enter /var/lib/vservers/*/var/log/syslog which gets expanded to the same thing as

Package: logcheck Version: 1.3.13 Severity: minor Tags: patch In Lenny it was possible to use wildcards in logcheck.logfiles. For example, I used: /var/log/HOSTS/*/*.log root at durer:~# su -s /bin/bash -c "bash -x /usr/sbin/logcheck" logcheck <cut> + read file + logoutput '/var/log/HOSTS/*/*.log' + file='/var/log/HOSTS/*/*.log' + debug 'logoutput called

Package: logcheck Version: 1.2.41 Problem: Logcheck try to detect if log file have been rotate or not by file size way. Possible attack: - current log file (sizeA) - run logcheck, (logcheck/logtail put inode in offsetfile), offset=sizeA - [attacker run attack 1] - run logrotate - [attacker run attack 2] - run logcheck may don't detect the rotation and don't check the log for attack 1

i am using libvirt-1.1.4 with xen(libxl). When destroying the VM its showing the following error : virsh # destroy 4 error: Failed to destroy domain 4 error: End of file while reading data: Input/output error error: One or more references were leaked after disconnect from the hypervisor error: Failed to reconnect to the hypervisor virsh # list error: failed to connect to the hypervisor error: no

Hi, I''ve just installed 0.22.2 and believe I''ve discovered a bug (or oversight). I have an exec like this: exec { "change-to-local-mirror": command => "sed -i ''s#\(KERNEL_REPO.*=\).*#\1 $mirror#'' ${rulefile}", path => "/usr/bin:/usr/sbin:/bin",

Hi all, I am using Puppet to execute an Expect script (http://expect.sourceforge.net) on a client. The Puppet recipe, test.pp, is: exec { ''/root/test.exp'': command => ''/root/test.exp'', logoutput => true } The recipe runs correctly when run using ''puppet --debug --verbose test.pp'': debug: /Stage[main]//Exec[/root/test.exp]:

Hi gang, While writing a script that uses logtail, I noticed that logtail assumes nothing interesting happened between its last invocation and the rotation, which means that exciting bits of data could be lost. This seems a bit dodgy (correct me if I'm wrong about how it works!) so I made a dodgy patch to logtail that checks for the existence of $logfile.0, which on Debian seems to always be

Hoping you guys might be able to help me out, I''m not sure what''s wrong but puppet agent hangs for over a minute, no resource spikes (CPU, memory, etc all stay basically the same as without starting puppet, barely a blip, and I''ve got more than enough headroom). It''s not a serious issue for continuous usage, but really, really annoying when testing the manifests

Hey team, I'll be at sea on and off this week, and as such my Internet access will depend on wifi availability while in port. 22a seems stable, but if any critical problems arise, feel free to prepare a release and bug Alfie to upload it. On the brighter side, I expect to be extremely bored while offline so I'll probably get some logcheck work done. <: Cheers, -- [ Todd J.

Hello, I'm having this error: Warning: If you are seeing this message, your log files may not have been checked! Details: Could not run logtail or save output Check temporary directory: /tmp/logcheck.EIX3jp declare -x HOME="/var/lib/logcheck" declare -x LANG="en_US" declare -x LANGUAGE="en_US:en_GB:en" declare -x LOGNAME="logcheck" declare -x

Hello, While some people might scuba dive, let's summarize recent progress and state (People cc'ed have either patches in queue or are involved): * Patches pending review, allmost ready for klibc ------------------------------------------------- - mikew/drop_cap - kinit: Add drop_capabilities support adds the ability to kinit to allow the dropping of POSIX capabilities. (patch even

Hi, One thing I''d like to be able to do is this... define sedfile ( $file = '''', $target = '''', $pattern = '''', $options = ''-i -n'' , onlyif = '''' ) { case $file { '''': { err ( "Require valid filename: ''$file''" ) } } case $target {

I have the following exec in my manifest : exec { some_exec: path => [ "/bin","/usr/bin","/usr/local/bin" ], command => "EXECUTE COMMAND 1", onlyif => "EXECUTE COMMAND 2", logoutput => "on_failure" } I want that the "COMMAND 1" should be executed by "USER 1" and "COMMAND 2"

so here I am trying to track down why one of my execs isn''t working properly and I notice in the wiki[1]the option on_failure for logoutput. Turns out it does''t work (in 0.23.0) err: Parameter logoutput failed: Invalid ''logoutput'' value "on_failure". Valid values are true, false, debug, info, notice, warning, err, alert, emerg, crit. err: Could not