similar to: "syslog is smaller" warning

Processing commands for control at bugs.debian.org: > clone 296096 -1 Bug#296096: logcheck shows the same month old logs again and again Bug 296096 cloned as bug 298206. > reassign -1 syslog-ng Bug#298206: logcheck shows the same month old logs again and again Bug reassigned from package `logcheck' to `syslog-ng'. > severity -1 minor Bug#298206: logcheck shows the same month

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

Package: logcheck Version: 1.2.58.0 Severity: wishlist Tags: patch The attached patch is the diff from current svn trunk to my svn branch zugschlus200707. It introduces a new binary package logtail2 with a new binary logtail2 which enhances logtail substantially. logtail2 can process rotated logs internally, which makes the code inside logcheck and other programs that use logtail2 easier to

hi before checking in that chown fix, i wanted you to take a look. tested on my workstation. basicaly the patch takes care that logtail saves the offset file with the correct permissions. when playing around lately with file tampering and those invoking logcheck as root. i got similar output to #253998 Alfie may point out that i should not invoke logcheck as root, but i better fix that before

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

--nextPart2699335.H7BBWTdPIb Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello :) After upgrading recently from Woody to Sarge (which went fairly well) I now= =20 have trouble with logcheck. I have been unable to track down a solution. Logcheck runs perfectly through the week until Sunday when logrotate does

Package: logcheck Severity: wishlist Currently syslog-summary is only enabled if it is installed and if it is enabled in logcheck's conffile. I think enabling it by default if syslog-summary is installed would be more sane. A new option -U "Disable syslog-summary" should be added in the assumedly rare case people want to disable it on the commandline although they installed

Package: logcheck-database Version: 1.2.43a Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I recently switched to syslog-ng. Here are some lines that can be ignored. syslog-ng: Changing permissions on special file /dev/xconsole syslog-ng: STATS: dropped 2 - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'),

Package: logcheck-database Version: 1.2.63 Severity: wishlist Hi, Can you add rule to filter out following messages: System Events =-=-=-=-=-=-= May 15 07:44:48 niko syslog-ng[21911]: Configuration reload request received, reloading configuration; Best regards Andrei Emeltchenko -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'),

Package: logcheck wanted to work on #195935, but found a less than funny issue, easy to reproduce: * remove some lines in front of your logfile * invoke logcheck you'll get a big email with all not matching lines from that log. not setting that to high priority because you are getting also the newer loglines. don't know if i find time that weekend. wanted to document it anyways. a++

Lorena, Primero felicitaciones por terminar el trabajo para publicar. Respecto de tu pregunta, quizas mejor si le preguntas a quien te hizo la pregunta. En mi sesion de R el resultado es el siguiente > citation() To cite R in publications use: R Core Team (2013). R: A language and environment for statistical computing. R Foundation for Statistical Computing, Vienna, Austria. URL

David Meyer wrote: > > Evan Zane Macosko wrote: > > > > Hello everyone. > > > > I am using the RPgSQL package, and am having some trouble using the > > db.execute command. I successfully connect to my database, and issue a > > simple SQL query, like db.execute("Select * from c0000075"), where > > c0000075 is a table in my database. But

Package: logcheck Version: 1.2.68 Severity: important I upgraded my lenny server today. I guess the previous update is something like two weeks ago. Now logcheck started sending mails containing only this perl error: This email is sent by logcheck. If you wish to no-longer receive it, you can either deinstall the logcheck package or modify its configuration file (/etc/logcheck/logcheck.conf).

SUBMISSION DEADLINE 9th International Conference on Pervasive and Embedded Computing and Communication Systems Submission Deadline: April 29, 2019 http://www.peccs.org/ September 19 - 20, 2019 Vienna, Austria. PECCS is organized in 5 major tracks: - Wireless and Mobile Technologies - Sensor Networks: Software, Architectures and Applications? - Intelligent Data Analysis and Processing -

SUBMISSION DEADLINE 9th International Conference on Pervasive and Embedded Computing and Communication Systems Submission Deadline: May 20, 2019 http://www.peccs.org/ September 19 - 20, 2019 Vienna, Austria. PECCS is organized in 5 major tracks: - Wireless and Mobile Technologies - Sensor Networks: Software, Architectures and Applications? - Intelligent Data Analysis and Processing -

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf:

Dear Spencer Thank you for this extensive explanation of the problem. I was just curious. Best regards Christian ============================================== Christian Stratowa, PhD Boehringer Ingelheim Austria Dept NCE Lead Discovery - Bioinformatics Dr. Boehringergasse 5-11 A-1121 Vienna, Austria Tel.: ++43-1-80105-2470 Fax: ++43-1-80105-2683 email: christian.stratowa at

hi all! I'm running an Asterisk-box with bristuff-....RC8n and 2 HFC-S cards. I m located in Vienna/Austria. I have the problem that on outgoing calls i hear my voice as a short echo (about half a second). This occurs not on every call. I tried some changes in my zapata.conf, with rxgain and txgain settings, but to me its hard to find a configuration which is good for every call i make. Is

DSC 2001 International Workshop on Distributed Statistical Computing http://www.ci.tuwien.ac.at/Conferences/DSC-2001 March 15--17, 2001 Vienna, Austria The second international workshop on `Distributed Statistical Computing' (DSC 2001) will take place at the Technische Universität Wien in Vienna, Austria from 2001-03-15 to 2001-03-17. This workshop will deal with future directions in

My subject line refers to a thread from June 2005 where I found explanations from Uwe Ligges and Friedrich Leisch as to what is intended by the R citation recommended within the software. Forgive me if I missed some points within the thread but when I found myself circling through messages I had already read, I stopped trying to follow it. I understand and mostly agree with how the R citation is