search for: troxel

Displaying 20 results from an estimated 154 matches for "troxel".

2006 May 04
7
windows / migration issues
...o errors, she just stops short of the latest version. hasn''t been a problem until now -- starting to play around w/ unit tests, and test:units doesn''t get the database to the latest version before running. this is problematic. anyone have any info regarding this? thanks, clint troxel
2004 May 15
1
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?" >...
2006 Jul 04
1
no such user
I have rules like this on my servers: ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ proftpd\[[[:digit:]]+\]: [._[:alnum:]-]+ \([._[:alnum:]-]+\[[[:digit:].]{7,15}\]\) (- )USER [-_.[:alnum:]]+: no such user found from [._[:alnum:]-]+ \[[[:digit:].]{7,15}\]\ to [[:digit:].]{7,15}:21$ basically, I just don't care about logins as nonexistent users, I get so many of those that I don't even
2005 Jun 03
2
[ttroxell@debian.org: Re: Logcheck rules from other packages]
I'm not sure if this message ever made it to you, Jamie. I had a reverse DNS problem shortly after it was sent. ----- Forwarded message from Todd Troxell <ttroxell at debian.org> ----- Date: Wed, 1 Jun 2005 01:22:18 -0400 From: Todd Troxell <ttroxell at debian.org> To: "Jamie L. Penman-Smithson" <jamie at silverdream.org> Subject: Re: Logcheck rules from other packages Hey Jamie, On Mon, May 30, 2005 at 09:57:32PM +01...
2020 Apr 01
5
Can't block intrusion
On 1 Apr 2020, at 22:14, Greg Troxel <gdt at lexort.com> wrote: > > I think you need to use tcpdump and turn up firewall debugging. sngrep is your friend …My bet is UDP vs TCP on firewall rules :-) Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermai...
2005 Dec 23
4
Bug#344553: logcheck: Fails silently to read config file
Package: logcheck Version: 1.2.42 Severity: minor Tags: patch Logcheck does not report any error if the config file is not readable or does not exists. This may easily happen, as logcheck is run as logcheck user and while one is testing a new configuration on live system with running configuration intact. Following fragment may help: # Now source the config file - before things that should
2004 Apr 22
2
IPsec - got ESP going, but not AH
Hi folks, I've been working on getting my WiFi network running with IPsec. I'm at the point where all traffic on the wifi subnet is encrypted (i.e. ESP). Then I tried to add AH to the equation. I failed. This picture describes the network setup: http://beta.freebsddiary.org/images/ipsec-wireless.gif Here's what I'm trying and failing with. With these rules, I get no
2004 Jun 04
2
Bug#252597: logcheck: user logchecks mails should be delivered to root
Package: logcheck Version: 1.2.20a Severity: important Since logcheck changed to run as user logcheck, the error mails of the cron daemon end up in /var/mail/logcheck where nobody reads them. Mails for logcheck should be aliased to root like all the other mails of system accounts. I was searching for a long time what was wrong with my logcheck not delivering any mails. The lock directory was
2001 Nov 15
1
Solaris 2.6: acomp failed for session.c
...do_child(Session *, const char *); void do_motd(void); int check_quietlogin(Session *, const char *); + #ifdef LOGIN_NEEDS_UTMPX + static void do_pre_login(Session *); + #endif static void do_authenticated1(Authctxt *); static void do_authenticated2(Authctxt *); FWIW, -- Rick Troxel rick at helix.nih.gov 301/435-2983 ///////////////////////////////////////////////////////////////// All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity. --Abd...
2004 Aug 28
1
Bug#268277: logcheck documentation bug
/usr/share/doc/logcheck-database/README.logcheck-database.gz Do you think that this file is insufficient, or did you just not see it? If the latter is the case, perhaps I should add a pointer to it in logcheck.8. Cheers, -- [ Todd J. Troxell ,''`. Student, Debian GNU/Linux Developer, SysAdmin, Geek : :' : http://debian.org || http://rapidpacket.com/~xtat `. `' `- ]
2006 Jul 03
1
New logcheck committer
Martin F. Krafft (madduck) has been added to the project. P.S. I'd like to get a release out sometime next week. -- Todd Troxell http://rapidpacket.com/~xtat -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20060703/ffbdd621/attachm...
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
On 5/22/23 07:13, Greg Troxel wrote: > gene heskett <gheskett at shentel.net> writes: > >> Which file in the nut I pulled a month ago, should I start with to get >> the new version actually running? I still get - -V=2.7.4 > > It is likely that you have built new nut but old nut is still on your &...
2006 Nov 14
16
memory issues -- mongrel part of the problem?
...- those thumbnail images are coming from the cache. Also: Server : Fedora Core 5 Mongrel: 0.3.13.3 mongrel_cluster: 0.2.0 I''m eternally grateful to anyone who can help me out with this! Sort of at the end of my rope. Thanks in advance, & hope your Tuesday is good. Clint -- clint troxel _ Open End Studios _ 307.413.0366 http://openendstudios.com
2005 Jan 23
2
logcheck-database -- volatile?
...ile is necessary. If you are more interessted in debian-volatile, you can join our mailing list and also reach us at #debian-volatile on irc.debian.org. For the list of mirrors, please see http://volatile.debian.net/mirrors.html Cheers, Andi ----- End forwarded message ----- -- [ Todd J. Troxell ,''`. Student, Debian GNU/Linux Developer, SysAdmin, Geek : :' : http://debian.org || http://rapidpacket.com/~xtat `. `' `- ] -------------- next part ---------...
2005 Feb 16
3
Bug#295560: logcheck: Please include filename when reporting "invalid regular expression"
Package: logcheck Version: 1.2.34 Severity: wishlist I have a couple of home-made logcheck ignore files, and happened to have one unescaped (and unmatched) `(' in one of the filter lines. Because of this, cron sent a mail with the body "grep: Invalid regular expression" - the subject is the command in the "2 * * * *" line in /etc/cron.d/logcheck, of course. It would be
2004 Dec 25
2
Bug#287184: logcheck overwriting ownership/permissions of /etc/logcheck/* on upgrades
Package: logcheck Version: 1.2.32 Severity: important In postinst logcheck "fixes" permissions of /etc/logcheck/* to 750. In my (and others on #d-d) opinion ownership and permissions should be preserved upon package upgrades. Logcheck must not screw with my decision to make them world readable every time it configures. -- Peter
2005 Jan 20
2
Bug#291395: logcheck-database: Rules dirs are setuid, they should be setgid
Package: logcheck-database Version: 1.2.33 Severity: normal I just installed 1.2.33, and it made my rules dirs setuid, not setgid... - Marc -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of
2005 Jan 09
2
Bug#289529: logcheck: "Ghandi" should be "Gandhi" in README.how.to.interpret
Package: logcheck Version: 1.2.32 Severity: minor "Ghandi" should be "Gandhi" in README.how.to.interpret, assuming that you mean the Indian freedom fighter M.K. Gandhi a.k.a. Mahatma Gandhi. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C
2023 May 22
3
got nut 2.8.1 but despite reinstall, shows 2.7.4
gene heskett <gheskett at shentel.net> writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (on NetBSD/pkgsrc, surely not what you are using).
2005 Jan 11
2
Bug#289801: Logtail should output error messages to stderr, not stdout
Package: logtail Version: 1.2.33 Severity: normal Hi... Logtail should not output error messages to standard output, since this violates the principle of least surprise. In particular, my application was broken by the semantics of logtail changing in version 1.2.21 (when you added switches for the default arguments to logtail). I think this was a bad move -- you broke an interface used by