search for: fbrier

...9;s log. I should point out that the server is 2.0.0. (Yeah, I know how old that is. Unfortunately, I only manage the client; the server is out of my hands.) Has anything changed in 2.0-kh60a that would require a more recent version of icecast? -- Fr?d?ric Bri?re <*> fbriere@fbriere.net => <fbriere@abacom.com> IS NO MORE: <http://www.abacomsucks.com> <=

hi, i am desperately trying to get this version of ices up and running on debian etch. i used the apt repository at http://www.fbriere.net/debian/ices2/ but i found this also affects the "official" source package at http://mediacast1.com/~karl/ when i try to run an edited version of either the example file provided with the source package or the deb at /usr/share/doc/ices2-kh/ i get: Failed to read config file &quot...

Package: logcheck Version: 1.2.39 Severity: normal Since I've upgraded my servers to sarge, I'm getting mail every hour for stuff that was duly included in /etc/logcheck/logcheck.ignore. Turns out that sarge's version no longer reads that file. If this was a conscious decision, then there should be some warning about this when upgrading (via debconf of NEWS.Debian). Also, the

Package: logcheck-database Version: 1.2.61 Severity: wishlist File: /etc/logcheck/ignore.d.server/proftpd Two weeks ago, I got a rush of these: Sep 8 12:37:07 goretex proftpd: PAM-listfile: Refused user news for service proftpd (Apparently, fail2ban managed to miss those.) This is triggered by pam_listfile, which is used by proftpd (and other FTP daemons) to block users listed in

Package: logtail Version: 1.2.68 Severity: normal Hi, logtail does not cleanly update from logtail2: $ sudo dpkg --install /var/cache/apt/archives/logtail_1.2.68_all.deb (Reading database ... 26564 files and directories currently installed.) Unpacking logtail (from .../logtail_1.2.68_all.deb) ... dpkg: error processing /var/cache/apt/archives/logtail_1.2.68_all.deb (--install): trying to

...ices_config->next_track = 0; return next_mod; } I've been running ices2 like this 24/7 for months now, only restarting it once a week for log rotation. Never had a problem since. -- Fr?d?ric Bri?re <*> fbriere@fbriere.net => <fbriere@abacom.com> IS NO MORE: <http://www.abacomsucks.com> <=

On Sun, 2005-02-20 at 12:15, Fr?d?ric Bri?re wrote: > I've been running ices2 like this 24/7 for months now, only restarting > it once a week for log rotation. Never had a problem since. setting <logsize> will cause an automatic log rotation when a certain file size has been reached. It renames <logfile> to <logfile>.1 then opens a new file <logfile> karl.

...signal(SIGHUP, signal_hup_handler); } @@ -67,6 +69,7 @@ void signals_setup(void) { + signal(SIGHUP, signal_hup_handler); signal(SIGINT, signal_int_handler); signal(SIGTERM, signal_int_handler); signal(SIGUSR1, signal_usr1_handler); -- Fr?d?ric Bri?re <*> fbriere@fbriere.net => <fbriere@abacom.com> IS NO MORE: <http://www.abacomsucks.com> <=

...recent version of icecast? > > wow, v2.0.0 is old, won't make a difference for the problem above but > other issues could show up. BTW, we just upgraded to 2.3.0 today, and kh60a still refuses to connect. Anything I can do to help? -- Fr?d?ric Bri?re <*> fbriere@fbriere.net => <fbriere@abacom.com> IS NO MORE: <http://www.abacomsucks.com> <=

...doesn't appear to be broadcasting. Yet it's not closing the connection either. I'm attaching ices2's config file. Any help or pointers would be appreciated; otherwise I'll have to sprinkle some fprintfs everywhere and hope for the best. :( -- Frederic Briere <*> fbriere@fbriere.net => <fbriere@abacom.com> IS NO MORE: <http://www.abacomsucks.com> <= -------------- next part -------------- A non-text attachment was scrubbed... Name: ices2.xml Type: text/xml Size: 2145 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast/atta...

hi everyone! currently, karl's branch of ices has a number of interesting features that the ices release does not: * jack support (very important for a number of users i know, and generally cool in terms of interoperability) * really nice metadata updates and on-the-fly savefile changes * runner threads for load distribution on smp boxen * on-the-fly switching of input sources (useful

...9 [cups-filters] cups-pdf: please change default output to embedded text rather than rasterized graphics Changed Bug submitter to 'Anders Lager?s <anders.lageras at gmail.com>' from 'Anders Lager??s <anders.lageras at gmail.com>' > submitter 526698 Fr?d?ric Bri?re <fbriere at fbriere.net> Bug #526698 {Done: Benjamin Drung <bdrung at debian.org>} [devscripts] [licensecheck] Remove assembler comments beginning with "@" or ";" Changed Bug submitter to 'Fr?d?ric Bri?re <fbriere at fbriere.net>' from 'Fr??d??ric Bri??re <...

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Package: logcheck-database Version: 1.2.54 Severity: normal I recently created a bridge with the name xen-local. The DHCP server gets requests via this bridge. I got spammed with logcheck messages about DHCPREQUESTS and the lot because the name of the interface in the logcheck-database does not match on names with a dash in it. -- System Information: Debian Release: 4.0 APT prefers stable

tobias wrote: > hi, > > i am desperately trying to get this version of ices up and running on debian > etch. i used the apt repository at http://www.fbriere.net/debian/ices2/ but i > found this also affects the "official" source package at > http://mediacast1.com/~karl/ > when i try to run an edited version of either the example file provided with > the source package or the deb at /usr/share/doc/ices2-kh/ i get: > > Fa...

Package: logcheck-database Version: 1.2.62 Severity: wishlist File: /etc/logcheck/ignore.d.server/ssh openssh issues a friendly warning when the remote IP maps back to a hostname that looks just like an IP address. (For example, the address 206.251.174.31 currently maps back to the hostname "206.251.174.31".) Here's a rule that filters out these unimportant messages: ^\w{3} [

Signed-off-by: Fr?d?ric Bri?re <fbriere at fbriere.net> --- rulefiles/linux/ignore.d.server/openvpn | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/rulefiles/linux/ignore.d.server/openvpn b/rulefiles/linux/ignore.d.server/openvpn index 68ebf8f..c57e3cb 100644 --- a/rulefiles/linux/ignore.d.server/openvpn ++...

...has been modified to no longer attach the ":port" part to "[undef]" -- probably to reflect a recent change in openvpn. Unfortunately, the rule no longer matches in etch, thus breaking the backport. Here's a patch to match both versions. Signed-off-by: Fr?d?ric Bri?re <fbriere at fbriere.net> --- rulefiles/linux/ignore.d.server/openvpn | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/rulefiles/linux/ignore.d.server/openvpn b/rulefiles/linux/ignore.d.server/openvpn index c57e3cb..1ea6068 100644 --- a/rulefiles/linux/ignore.d.server/openvpn ++...

Package: logcheck-database Version: 1.2.63 Severity: normal Given that violations.d/logcheck has been emptied by 2394562ab4a13c4510c671f01ffc8f35e97f1cd3, shouldn't most of violations.ignore.d be moved to one of ignore.d.*? AIUI, all of these are currently rendered useless. (I'll gladly lend a hand; I just want to make sure this is the right thing to do.) -- System Information: Debian

I ran into the same problem after somebody uninstalled logcheck and I re-installed it. It turned out that the ownership of /var/lock/logcheck where root:root - sudo chown logcheck:logcheck /var/lock/logcheck solved it. I see that there already is a check for the permissions in the postinst which (as far as I can see) *should* have fixed the permissions and ownership there. When re-installing