Re: ncurses message spam
On Fri 21 Jun 15:23, Shawn Webb wrote: > Hey all, > > With the recent changes to ncurses in base, I'm getting a bunch of > messages (snippet below) on every single new PTY. Every time I open a > new window in tmux or login via ssh, I'm getting spammed with a flood > of messages like below. > > BEGIN LOG > Name collision 'tvi950-b' between > tvi950-b|bare tvi950 no is > and tvi950-b|bare tvi950 no is > ...now bare tvi950 no is > Cannot remove alias 'bare tvi950 no is' > Name collision 'tvi950-ns' between > tvi950-ns|tvi950 w/no standout > and tvi950-ns|tvi950 w/no standout > ...now tvi950 w/no standout > Cannot remove alias 'tvi950 w/no standout' > Name collision 'tvi925' between > tvi925|925|televideo model 925 > and tvi925|925|televideo model 925 > ...now 925|televideo model 925 > ...now televideo model 925 > Cannot remove alias 'televideo model 925' > Name collision 'tvi925vb' between > tvi925vb|925vb|televideo model 925 visual bells > and tvi925vb|925vb|televideo model 925 visual bells > ...now 925vb|televideo model 925 visual bells > ...now televideo model 925 visual bells > Cannot remove alias 'televideo model 925 visual bells' > Name collision 'tvi925n' between > > tvi925n|925n|televideo model 925 no standout or underline > and tvi925n|925n|televideo model 925 no standout or underline > ...now 925n|televideo model 925 no standout or underline > ...now televideo model 925 no standout or underline > Cannot remove alias 'televideo model 925 no standout or underline' > Name collision 'tvi925vbn' between > tvi925vbn|925vbn|televideo model 925 visual bells no so or ul > and tvi925vbn|925vbn|televideo model 925 visual bells no so or ul > ...now 925vbn|televideo model 925 visual bells no so or ul > ...now televideo model 925 visual bells no so or ul > Cannot remove alias 'televideo model 925 visual bells no so or ul' > Name collision '925a' between > 925a|tvi925a|TeleVideo Model 925 > and 925a|tvi925a|TeleVideo Model 925 > ...now tvi925a|TeleVideo Model 925 > ...now TeleVideo Model 925 > Cannot remove alias 'TeleVideo Model 925' > Name collision 'tvi950' between > > > tvi950|950|televideo950 > and tvi950|950|televideo950 > > > ...now 950|televideo950 > > > ...now televideo950 > > > Cannot remove alias 'televideo950' > END LOG > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 > https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc Do your sync again, this has been fixed a few hours after the ncurses 6.5 upgrade Bapt
ncurses message spam
Hey all, With the recent changes to ncurses in base, I'm getting a bunch of messages (snippet below) on every single new PTY. Every time I open a new window in tmux or login via ssh, I'm getting spammed with a flood of messages like below. BEGIN LOG Name collision 'tvi950-b' between tvi950-b|bare tvi950 no is and tvi950-b|bare tvi950 no is ...now bare tvi950 no is Cannot remove alias 'bare tvi950 no is' Name collision 'tvi950-ns' between tvi950-ns|tvi950 w/no standout and tvi950-ns|tvi950 w/no standout ...now tvi950 w/no standout Cannot remove alias 'tvi950 w/no standout' Name collision 'tvi925' between tvi925|925|televideo model 925 and tvi925|925|televideo model 925 ...now 925|televideo model 925 ...now televideo model 925 Cannot remove alias 'televideo model 925' Name collision 'tvi925vb' between tvi925vb|925vb|televideo model 925 visual bells and tvi925vb|925vb|televideo model 925 visual bells ...now 925vb|televideo model 925 visual bells ...now televideo model 925 visual bells Cannot remove alias 'televideo model 925 visual bells' Name collision 'tvi925n' between tvi925n|925n|televideo model 925 no standout or underline and tvi925n|925n|televideo model 925 no standout or underline ...now 925n|televideo model 925 no standout or underline ...now televideo model 925 no standout or underline Cannot remove alias 'televideo model 925 no standout or underline' Name collision 'tvi925vbn' between tvi925vbn|925vbn|televideo model 925 visual bells no so or ul and tvi925vbn|925vbn|televideo model 925 visual bells no so or ul ...now 925vbn|televideo model 925 visual bells no so or ul ...now televideo model 925 visual bells no so or ul Cannot remove alias 'televideo model 925 visual bells no so or ul' Name collision '925a' between 925a|tvi925a|TeleVideo Model 925 and 925a|tvi925a|TeleVideo Model 925 ...now tvi925a|TeleVideo Model 925 ...now TeleVideo Model 925 Cannot remove alias 'TeleVideo Model 925' Name collision 'tvi950' between tvi950|950|televideo950 and tvi950|950|televideo950 ...now 950|televideo950 ...now televideo950 Cannot remove alias 'televideo950' END LOG Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: Spam mail being sent via the FreeBSD mailing lists
Well, if you require "FreeBSD" somewhere in the letter with exception of "To" field it would be quite enough. You only have to announce that the "FreeBSD" keyword should be included. "Linux" is optional. Spammers have no idea what FreeBSD is. On 5/26/21 1:34 PM, Kurt Jaeger wrote: Hi! On May 25, 2021, at 8:53 PM, jake h wrote: I have recently received several pieces of spam mail, apparently sent via this mailing list. These pieces of mail are the usual spam formula; Your phone has a virus, Ads, Fake blackmail, so on and so forth. Has anyone else noticed these spam emails, or is it just me? I'm receiving these too. It looks like the servers are bouncing some of them just for me, even. And I'm receiving not just from this list; also from freebsd-hackers@ and ports@. postmaster@ is aware of the problem, we do not yet have a clear-cut solution and we're investigating.
Re: Spam mail being sent via the FreeBSD mailing lists
On 2021-05-26 22:50:57 (+0800), Julian H. Stacey wrote: Kurt Jaeger wrote: Hi! On May 25, 2021, at 8:53 PM, jake h wrote: I have recently received several pieces of spam mail, apparently sent via this mailing list. These pieces of mail are the usual spam formula; Your phone has a virus, Ads, Fake blackmail, so on and so forth. Has anyone else noticed these spam emails, or is it just me? I'm receiving these too. It looks like the servers are bouncing some of them just for me, even. And I'm receiving not just from this list; also from freebsd-hackers@ and ports@. postmaster@ is aware of the problem, we do not yet have a clear-cut solution and we're investigating. -- p...@opsec.eu+49 171 3101372Now what ? I'm on most lists & also seen much spam lately. Changing Mailman list configs to only allowing postings from subscribed addresses could dump nearly all spam; (I'm a Mailman admin elsewhere ). This was how the majority of FreeBSD mailing lists were configured. Most lists were set to discard postings from non-subscribers. Some were set to hold. A few were set to reject. But @freebsd.org has prefered open lists for near all lists. Best only for the initial fresh- after- install- questions@, IMO. This has not been true for a good while now. Historically, nearly all our lists were indeed open. In recent years, we've made most lists subscriber-only, with some exceptions and whitelists. List back end responses to eg isp@ & hackers@ have recently migrated from Mailman to Mlmmj, I guess that shouldn't directly affect spam protection ? but it'd be interesting to know what advantage the migration might bring @freebsd.org ? For one thing, running supported software means we can continue upgrading our mailservers with fewer worries. Mailman 2 relies on Python 2, which has unfortunately become abandonware. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Re: Spam mail being sent via the FreeBSD mailing lists
from Kurt Jaeger: > Hi! > > > On May 25, 2021, at 8:53 PM, jake h wrote: > > > I have recently received several pieces of spam mail, apparently sent via > > > this mailing list. These pieces of mail are the usual spam formula; Your > > > phone has a virus, Ads, Fake blackmail, so on and so forth. > > > Has anyone else noticed these spam emails, or is it just me? > > I'm receiving these too. It looks like the servers are bouncing some of > > them just for me, even. And I'm receiving not just from this list; also > > from freebsd-hackers@ and ports@. > postmaster@ is aware of the problem, we do not yet have a clear-cut > solution and we're investigating. Maybe the problem of bouncing messages is related to the spam problem? I notice now there is an epidemic of multipart/alternative messages on FreeBSD lists, which is a recent change, not for the better. I posted, several days ago (May 22), a question about bouncing messages, that was on freebsd-questi...@freebsd.org . Tom
Re: Spam mail being sent via the FreeBSD mailing lists
Kurt Jaeger wrote: > Hi! > > > On May 25, 2021, at 8:53 PM, jake h wrote: > > > I have recently received several pieces of spam mail, apparently sent via > > > this mailing list. These pieces of mail are the usual spam formula; Your > > > phone has a virus, Ads, Fake blackmail, so on and so forth. > > > Has anyone else noticed these spam emails, or is it just me? > > I'm receiving these too. It looks like the servers are bouncing some of > > them just for me, even. And I'm receiving not just from this list; also > > from freebsd-hackers@ and ports@. > > postmaster@ is aware of the problem, we do not yet have a clear-cut > solution and we're investigating. > -- > p...@opsec.eu +49 171 3101372Now what ? I'm on most lists & also seen much spam lately. Changing Mailman list configs to only allowing postings from subscribed addresses could dump nearly all spam; (I'm a Mailman admin elsewhere ). But @freebsd.org has prefered open lists for near all lists. Best only for the initial fresh- after- install- questions@, IMO. Mailman can also input from a spam phrases block list, though I haven't much used that on lists I run, as subscriber only block near all. Normaly the @freebsd.org anti spam mechanisms protect both lists & non lists. List back end responses to eg isp@ & hackers@ have recently migrated from Mailman to Mlmmj, I guess that shouldn't directly affect spam protection ? but it'd be interesting to know what advantage the migration might bring @freebsd.org ? ( Though I couldn't migrate most lists I run from Mailman to Mlmmj, as many lists I run are mostly non techs, incompetent with anything beyond click & fumble. Command lines of Majordomo & Mlmmj impossible for them ) Cheers, -- Julian Stacey http://berklix.com/jhs/ http://stolenvotes.uk http://www.berklix.org/~jhs/mail/sorbs/ Unreliable spam black list extorter.
Re: Spam mail being sent via the FreeBSD mailing lists
Hi! > > On May 25, 2021, at 8:53 PM, jake h wrote: > > I have recently received several pieces of spam mail, apparently sent via > > this mailing list. These pieces of mail are the usual spam formula; Your > > phone has a virus, Ads, Fake blackmail, so on and so forth. > > Has anyone else noticed these spam emails, or is it just me? > I'm receiving these too. It looks like the servers are bouncing some of them > just for me, even. And I'm receiving not just from this list; also from > freebsd-hackers@ and ports@. postmaster@ is aware of the problem, we do not yet have a clear-cut solution and we're investigating. -- p...@opsec.eu+49 171 3101372Now what ?
Re: Spam mail being sent via the FreeBSD mailing lists
> On May 25, 2021, at 8:53 PM, jake h wrote: > > I have recently received several pieces of spam mail, apparently sent via > this mailing list. These pieces of mail are the usual spam formula; Your > phone has a virus, Ads, Fake blackmail, so on and so forth. > Has anyone else noticed these spam emails, or is it just me? I'm receiving these too. It looks like the servers are bouncing some of them just for me, even. And I'm receiving not just from this list; also from freebsd-hackers@ and ports@. -- rollingbits — 📧 rollingb...@icloud.com 📧 rollingb...@gmail.com 📧 rollingb...@yahoo.com 📧 rollingb...@terra.com.br 📧 rollingb...@globo.com
Re: Spam mail being sent via the FreeBSD mailing lists
I got one this morning Blackmail stuff - just delete it. > On May 25, 2021, at 4:52 PM, jake h wrote: > > Hi everyone, > I have recently received several pieces of spam mail, apparently sent via > this mailing list. These pieces of mail are the usual spam formula; Your > phone has a virus, Ads, Fake blackmail, so on and so forth. > Has anyone else noticed these spam emails, or is it just me? > Thanks, > Jake
Spam mail being sent via the FreeBSD mailing lists
Hi everyone, I have recently received several pieces of spam mail, apparently sent via this mailing list. These pieces of mail are the usual spam formula; Your phone has a virus, Ads, Fake blackmail, so on and so forth. Has anyone else noticed these spam emails, or is it just me? Thanks, Jake
Re: How to delete comment spam from bugzilla?
Hello, From: Alan Somers Subject: How to delete comment spam from bugzilla? Date: Fri, 23 Apr 2021 09:31:01 -0600 > Somebody, or more likely some bot, is posting comment spam in our > bugzilla. How can we delete spammy comments ? I faced same situation before and was told to send mail to bugmeis...@freebsd.org. --- Yasuhiro Kimura ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
How to delete comment spam from bugzilla?
Somebody, or more likely some bot, is posting comment spam in our bugzilla. How can we delete spammy comments ? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: console spam during mergemaster
On Sun, Jul 29, 2018 at 7:05 AM, O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Sun, 29 Jul 2018 08:58:47 -0400 > Michael Butler schrieb: > > > This started a few days ago .. no apparent ill effect but still annoying > .. > > > > *** Creating the temporary root environment in /var/tmp/temproot > > *** /var/tmp/temproot ready for use > > *** Creating and populating directory structure in /var/tmp/temproot > > > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined > here > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined > here > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > > script for target "/var/tmp/temproot/etc/pam.d" ignored > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > > previous script for "/var/tmp/temproot/etc/pam.d" defined here > > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > > script for target "/var/tmp/temproot/etc/pam.d" ignored > > > > imb > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > freebsd.org" > > me, too > > Regards, > > oh > > - -- > O. Hartmann > > Ich widerspreche der Nutzung oder Übermittlung meiner Daten für > Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). > -BEGIN PGP SIGNATURE- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW127wgAKCRDS528fyFhY > lDBdAf4mFhRmAWPot0FZZ6+/Z8TuTej/zrcxTs5S0sAQOzTHmoFu43huiwUJbs6Z > 8DMEik2T+ynJf4ocf1+UxAkyNKgmAf0e7aerKYCqGKg5QCP3zSS3TpdERnxWPVMn > b/LVa0kyJzzU1vnxBhj9LNoCrAlIV27J8JtxNP7db9Csvygaks7/ > =e7SV > -END PGP SIGNATURE- It's caused by r336640. I've let the committer know. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: console spam during mergemaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Sun, 29 Jul 2018 08:58:47 -0400 Michael Butler schrieb: > This started a few days ago .. no apparent ill effect but still annoying .. > > *** Creating the temporary root environment in /var/tmp/temproot > *** /var/tmp/temproot ready for use > *** Creating and populating directory structure in /var/tmp/temproot > > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > script for target "/var/tmp/temproot/etc/periodic/daily" ignored > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > previous script for "/var/tmp/temproot/etc/periodic/daily" defined here > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > script for target "/var/tmp/temproot/etc/periodic/monthly" ignored > make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate > script for target "/var/tmp/temproot/etc/pam.d" ignored > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using > previous script for "/var/tmp/temproot/etc/pam.d" defined here > make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate > script for target "/var/tmp/temproot/etc/pam.d" ignored > > imb > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" me, too Regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW127wgAKCRDS528fyFhY lDBdAf4mFhRmAWPot0FZZ6+/Z8TuTej/zrcxTs5S0sAQOzTHmoFu43huiwUJbs6Z 8DMEik2T+ynJf4ocf1+UxAkyNKgmAf0e7aerKYCqGKg5QCP3zSS3TpdERnxWPVMn b/LVa0kyJzzU1vnxBhj9LNoCrAlIV27J8JtxNP7db9Csvygaks7/ =e7SV -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
console spam during mergemaster
This started a few days ago .. no apparent ill effect but still annoying .. *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/daily" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/daily" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/daily" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/daily" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/monthly" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/periodic/monthly" ignored make[4]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/periodic/monthly" defined here make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 29: warning: duplicate script for target "/var/tmp/temproot/etc/pam.d" ignored make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: using previous script for "/var/tmp/temproot/etc/pam.d" defined here make[3]: "/usr/src/share/mk/bsd.dirs.mk" line 31: warning: duplicate script for target "/var/tmp/temproot/etc/pam.d" ignored imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Spam in console after r336593 (NFS mounted)
Hello. After https://svnweb.freebsd.org/base?view=revision&revision=336593 any make action starting spam errors (svn not work on NFS mounted partitions) svn: E155016: The working copy database at '/usr/src' is corrupt. svn: E155016: The working copy database at '/usr/src' is corrupt. make[2]: "/usr/src/release/Makefile.ec2" line 24: warning: "/usr/local/bin/svn info --show-item last-changed-revision /usr/sr c/release/.." returned non-zero status svn: E155016: The working copy database at '/usr/src' is corrupt. svn: E155016: The working copy database at '/usr/src' is corrupt. make[2]: "/usr/src/release/Makefile.ec2" line 24: warning: "/usr/local/bin/svn info --show-item last-changed-revision /usr/sr c/release/.." returned non-zero status ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: DNSSEC/Log Spam for partially DNSSEC domain
On 30 Jun 2018, at 04:03, Larry Rosenman wrote: > > I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is > DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due > to HE.net don't support DNSSEC. > > I get a ton of: > Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked for > "borg.lerctr.org IN ", got type "RRSIG" > Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked for > "borg.lerctr.org IN A", got type "RRSIG" > > in my logs, which comes from libc: > /usr/src/lib/libc/net/getaddrinfo.c: > 2092 #ifdef DEBUG > 2093 if (type != T_KEY && type != T_SIG && > 2094 type != ns_t_dname) > 2095 syslog(LOG_NOTICE|LOG_AUTH, > 2096"gethostby*.getanswer: asked for \"%s %s %s\", got type > \"%s\"", > 2097qname, p_class(C_IN), > p_type(qtype), > 2098p_type(type)); > 2099 #endif > > Is there an easy way to make this quieter? I see this code is only included if DEBUG is defined. Maybe undefine DEBUG, for this particular file? Or hack it so it has #undef DEBUG at the top? That said, I'm not sure if debug messages like this should be enabled by default, and impossible to squelch without recompiling libc. So maybe we should #if 0 it, instead. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: DNSSEC/Log Spam for partially DNSSEC domain
On Fri, Jun 29, 2018 at 07:33:02PM -0700, Michael Mitchell wrote: > /etc/syslog.conf maybe > > mdm - from a phone > That won't help, as I don't want to suppress ALL of the nastygrams. I'm looking for more selectivity from this in libc. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 signature.asc Description: PGP signature
Re: DNSSEC/Log Spam for partially DNSSEC domain
On Fri, Jun 29, 2018 at 08:29:48PM -0700, Michael Mitchell wrote: > pick the right options for the daemon and info level? Nope, it's just this message which is annoying. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 signature.asc Description: PGP signature
Re: DNSSEC/Log Spam for partially DNSSEC domain
pick the right options for the daemon and info level? mdm - from a phone On Fri, Jun 29, 2018, 8:00 PM Larry Rosenman wrote: > On Fri, Jun 29, 2018 at 07:33:02PM -0700, Michael Mitchell wrote: > > /etc/syslog.conf maybe > > > > mdm - from a phone > > > That won't help, as I don't want to suppress ALL of the nastygrams. > > I'm looking for more selectivity from this in libc. > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: l...@lerctr.org > US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: DNSSEC/Log Spam for partially DNSSEC domain
/etc/syslog.conf maybe mdm - from a phone On Fri, Jun 29, 2018, 7:27 PM Larry Rosenman wrote: > I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is > DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due > to HE.net don't support DNSSEC. > > I get a ton of: > Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked > for "borg.lerctr.org IN ", got type "RRSIG" > Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked > for "borg.lerctr.org IN A", got type "RRSIG" > > in my logs, which comes from libc: > /usr/src/lib/libc/net/getaddrinfo.c: >2092 #ifdef DEBUG >2093 if (type != T_KEY && type != T_SIG && >2094 type != ns_t_dname) >2095 syslog(LOG_NOTICE|LOG_AUTH, >2096"gethostby*.getanswer: asked for \"%s %s %s\", got > type \"%s\"", >2097qname, p_class(C_IN), > p_type(qtype), >2098p_type(type)); >2099 #endif > > Is there an easy way to make this quieter? > > > > > -- > Larry Rosenman https://people.FreeBSD.org/~ler/ > Phone: +1 214-642-9640 E-Mail: l...@freebsd.org > US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
DNSSEC/Log Spam for partially DNSSEC domain
I'm running Exim, with DNSSEC enabled, and my zone (lerctr.org) is DNSSEC signed, but my dyn.lerctr.org subdomain is NOT DNSSEC signed due to HE.net don't support DNSSEC. I get a ton of: Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked for "borg.lerctr.org IN ", got type "RRSIG" Jun 29 20:12:53 thebighonker exim[37649]: gethostby*.gethostanswer: asked for "borg.lerctr.org IN A", got type "RRSIG" in my logs, which comes from libc: /usr/src/lib/libc/net/getaddrinfo.c: 2092 #ifdef DEBUG 2093 if (type != T_KEY && type != T_SIG && 2094 type != ns_t_dname) 2095 syslog(LOG_NOTICE|LOG_AUTH, 2096"gethostby*.getanswer: asked for \"%s %s %s\", got type \"%s\"", 2097qname, p_class(C_IN), p_type(qtype), 2098p_type(type)); 2099 #endif Is there an easy way to make this quieter? -- Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: l...@freebsd.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 signature.asc Description: PGP signature
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Thu., 22 Dec. 2016 at 12:45 am, Gleb Smirnoff wrote: > That was my failure and already fixed. > Thanks for the fix! For those of us playing along at home, I believe the fix can in r310032. https://svnweb.freebsd.org/base?view=revision&revision=310032 Regards, Ben ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Wed, Dec 21, 2016 at 11:03:14AM +0100, Eivind Nicolay Evensen wrote: E> E> On Tue, Dec 13, 2016 at 09:48:59AM -0600, Eric van Gyzen wrote: E> > On 12/13/2016 09:24, Michael Butler wrote: E> > > Any hints as to why all of my -current equipment is complaining like below. Is E> > > there a sysctl to moderate/turn this off? E> > > E> > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 E> > > packets/sec E> > > Dec 13 10:00:21 archive last message repeated 13 times E> > > Dec 13 10:02:21 archive last message repeated 18 times E> > > Dec 13 10:06:21 archive last message repeated 36 times E> > > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 E> > > packets/sec E> E> E> I repeated that on the nearest 10.0 here, because this looked strange, and E> indeed I see: E> Limiting icmp ping response from 294 to 200 packets/sec This is what should happen. E> However, the quoted line above that says it is limiting from 1 to 200 E> doesn't sound much of a limit? That was my failure and already fixed. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Tue, Dec 13, 2016 at 09:48:59AM -0600, Eric van Gyzen wrote: > On 12/13/2016 09:24, Michael Butler wrote: > > Any hints as to why all of my -current equipment is complaining like below. > > Is > > there a sysctl to moderate/turn this off? > > > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 > > packets/sec > > Dec 13 10:00:21 archive last message repeated 13 times > > Dec 13 10:02:21 archive last message repeated 18 times > > Dec 13 10:06:21 archive last message repeated 36 times > > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 > > packets/sec I repeated that on the nearest 10.0 here, because this looked strange, and indeed I see: Limiting icmp ping response from 294 to 200 packets/sec However, the quoted line above that says it is limiting from 1 to 200 doesn't sound much of a limit? -- Eivind N. Evensen ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Tue, Dec 13, 2016 at 11:07:19AM -0500, Michael Butler wrote: M> >> Any hints as to why all of my -current equipment is complaining like below. Is M> >> there a sysctl to moderate/turn this off? M> >> M> >> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:00:21 archive last message repeated 13 times M> >> Dec 13 10:02:21 archive last message repeated 18 times M> >> Dec 13 10:06:21 archive last message repeated 36 times M> >> Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:08:21 archive last message repeated 17 times M> >> Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200 M> >> packets/sec M> >> Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:10:21 archive last message repeated 17 times M> >> Dec 13 10:12:21 archive last message repeated 18 times M> >> Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> > M> > What Subversion revision are you running? Did this start happening after a M> > recent update? I ask because r309745 was committed a few days ago and might M> > have changed the behavior. M> M> That's consistent with my observations. I was in Australia for a couple M> of weeks and have just updated from SVN r309056 to r309852, The r310032 should fix it. I'm sorry for the problem. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 2016-12-13 10:24, Michael Butler wrote: > Any hints as to why all of my -current equipment is complaining like > below. Is there a sysctl to moderate/turn this off? > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to > 200 packets/sec > Dec 13 10:00:21 archive last message repeated 13 times > Dec 13 10:02:21 archive last message repeated 18 times > Dec 13 10:06:21 archive last message repeated 36 times > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to > 200 packets/sec > Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to > 200 packets/sec > Dec 13 10:08:21 archive last message repeated 17 times > Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 > to 200 packets/sec > Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to > 200 packets/sec > Dec 13 10:10:21 archive last message repeated 17 times > Dec 13 10:12:21 archive last message repeated 18 times > Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to > 200 packets/sec > Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to > 200 packets/sec > Dec 13 10:14:21 archive last message repeated 17 times > Dec 13 10:16:21 archive last message repeated 18 times > > Michael > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Yeah, this is a bug. When working as intended, the message would read: kernel: Limiting closed port RST response from 201 to 200 packets/sec The first value would be higher than the 2nd value (net.inet.icmp.icmplim). It should only alert if it is actually limiting the response rate. You can mute it by setting: net.inet.icmp.icmplim_output=0 -- Allan Jude ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Tue, Dec 13, 2016 at 11:19:18AM -0500, Michael Butler wrote: > On 12/13/16 11:15, Gary Palmer wrote: > > On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote: > >> On 12/13/16 10:29, Dimitry Andric wrote: > >> > >>> Somebody is most likely port scanning your machines. I see this all the > >>> time on boxes connected to the internet. > >> > >> As are mine. I wouldn't mind so much if the message contained sufficient > >> useful information that could be acted on, e.g. originating IP address > >> and, when appropriate, destination port. > > > > sysctl net.inet.tcp.log_in_vain=1 > > sysctl net.inet.udp.log_in_vain=1 > > > > be prepared for a lot of logs if you are being port scanned > > Or, apparently, have a windoze box on that segment :-( Windows client boxes at least do a lot of broadcasts, but in my experience they don't trigger log_in_vain (maybe they will if you have promisc network interfaces enabled). Not sure about servers as I don't have any at home. Gary ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Tue, Dec 13, 2016 at 11:07:19AM -0500, Michael Butler wrote: M> On 12/13/16 10:48, Eric van Gyzen wrote: M> > On 12/13/2016 09:24, Michael Butler wrote: M> >> Any hints as to why all of my -current equipment is complaining like below. Is M> >> there a sysctl to moderate/turn this off? M> >> M> >> Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:00:21 archive last message repeated 13 times M> >> Dec 13 10:02:21 archive last message repeated 18 times M> >> Dec 13 10:06:21 archive last message repeated 36 times M> >> Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:08:21 archive last message repeated 17 times M> >> Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200 M> >> packets/sec M> >> Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:10:21 archive last message repeated 17 times M> >> Dec 13 10:12:21 archive last message repeated 18 times M> >> Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 M> >> packets/sec M> >> Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 M> >> packets/sec M> > M> > What Subversion revision are you running? Did this start happening after a M> > recent update? I ask because r309745 was committed a few days ago and might M> > have changed the behavior. M> M> That's consistent with my observations. I was in Australia for a couple M> of weeks and have just updated from SVN r309056 to r309852, Yes, this is our fail. I will take a look today. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 12/13/16 11:15, Gary Palmer wrote: On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote: On 12/13/16 10:29, Dimitry Andric wrote: Somebody is most likely port scanning your machines. I see this all the time on boxes connected to the internet. As are mine. I wouldn't mind so much if the message contained sufficient useful information that could be acted on, e.g. originating IP address and, when appropriate, destination port. sysctl net.inet.tcp.log_in_vain=1 sysctl net.inet.udp.log_in_vain=1 be prepared for a lot of logs if you are being port scanned Or, apparently, have a windoze box on that segment :-( Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On Tue, Dec 13, 2016 at 10:43:27AM -0500, Michael Butler wrote: > On 12/13/16 10:29, Dimitry Andric wrote: > > > Somebody is most likely port scanning your machines. I see this all the > > time on boxes connected to the internet. > > As are mine. I wouldn't mind so much if the message contained sufficient > useful information that could be acted on, e.g. originating IP address > and, when appropriate, destination port. sysctl net.inet.tcp.log_in_vain=1 sysctl net.inet.udp.log_in_vain=1 be prepared for a lot of logs if you are being port scanned Regards, Gary ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 12/13/16 10:48, Eric van Gyzen wrote: On 12/13/2016 09:24, Michael Butler wrote: Any hints as to why all of my -current equipment is complaining like below. Is there a sysctl to moderate/turn this off? Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:00:21 archive last message repeated 13 times Dec 13 10:02:21 archive last message repeated 18 times Dec 13 10:06:21 archive last message repeated 36 times Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 packets/sec Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:08:21 archive last message repeated 17 times Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200 packets/sec Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:10:21 archive last message repeated 17 times Dec 13 10:12:21 archive last message repeated 18 times Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 packets/sec Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec What Subversion revision are you running? Did this start happening after a recent update? I ask because r309745 was committed a few days ago and might have changed the behavior. That's consistent with my observations. I was in Australia for a couple of weeks and have just updated from SVN r309056 to r309852, Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 2016/12/13 15:43, Michael Butler wrote: > On 12/13/16 10:29, Dimitry Andric wrote: > >> Somebody is most likely port scanning your machines. I see this all the >> time on boxes connected to the internet. > > As are mine. I wouldn't mind so much if the message contained sufficient > useful information that could be acted on, e.g. originating IP address > and, when appropriate, destination port. If you want that sort of information, you can use pf(4) with a default rule to log and reject connections to your system. (Plus rules to permit traffic to legitimate services, obviously.) You can also just 'drop' the denied connections rather than the default response of sending back an ICMP unreachable or reset response, which will save you sending out a lot of itty-bitty packets that the port scanners wouldn't pay attention to anyhow. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 12/13/2016 09:24, Michael Butler wrote: > Any hints as to why all of my -current equipment is complaining like below. Is > there a sysctl to moderate/turn this off? > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:00:21 archive last message repeated 13 times > Dec 13 10:02:21 archive last message repeated 18 times > Dec 13 10:06:21 archive last message repeated 36 times > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 > packets/sec > Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:08:21 archive last message repeated 17 times > Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to > 200 > packets/sec > Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:10:21 archive last message repeated 17 times > Dec 13 10:12:21 archive last message repeated 18 times > Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 > packets/sec > Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec What Subversion revision are you running? Did this start happening after a recent update? I ask because r309745 was committed a few days ago and might have changed the behavior. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 12/13/16 10:29, Dimitry Andric wrote: Somebody is most likely port scanning your machines. I see this all the time on boxes connected to the internet. As are mine. I wouldn't mind so much if the message contained sufficient useful information that could be acted on, e.g. originating IP address and, when appropriate, destination port. sysctl net.inet.icmp.icmplim_output=0, or increase the ICMP limit, if you want to help the port scanners. :-) I've added the sysctl to mute the warnings - thanks :-) Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Log spam: Limiting * response from 1 to 200 packets/sec
On 13 Dec 2016, at 16:24, Michael Butler wrote: > > Any hints as to why all of my -current equipment is complaining like below. Somebody is most likely port scanning your machines. I see this all the time on boxes connected to the internet. > Is there a sysctl to moderate/turn this off? > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:00:21 archive last message repeated 13 times > Dec 13 10:02:21 archive last message repeated 18 times > Dec 13 10:06:21 archive last message repeated 36 times > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 > packets/sec > Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:08:21 archive last message repeated 17 times > Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to > 200 packets/sec > Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:10:21 archive last message repeated 17 times > Dec 13 10:12:21 archive last message repeated 18 times > Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 > packets/sec > Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:14:21 archive last message repeated 17 times > Dec 13 10:16:21 archive last message repeated 18 times sysctl net.inet.icmp.icmplim_output=0, or increase the ICMP limit, if you want to help the port scanners. :-) -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Log spam: Limiting * response from 1 to 200 packets/sec
Any hints as to why all of my -current equipment is complaining like below. Is there a sysctl to moderate/turn this off? Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:00:21 archive last message repeated 13 times Dec 13 10:02:21 archive last message repeated 18 times Dec 13 10:06:21 archive last message repeated 36 times Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200 packets/sec Dec 13 10:07:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:08:21 archive last message repeated 17 times Dec 13 10:08:37 archive kernel: Limiting closed port RST response from 4 to 200 packets/sec Dec 13 10:09:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:10:21 archive last message repeated 17 times Dec 13 10:12:21 archive last message repeated 18 times Dec 13 10:12:28 archive kernel: Limiting icmp ping response from 1 to 200 packets/sec Dec 13 10:13:55 archive kernel: Limiting icmp unreach response from 1 to 200 packets/sec Dec 13 10:14:21 archive last message repeated 17 times Dec 13 10:16:21 archive last message repeated 18 times Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New spam on all my current machine consoles
On Tue, 2014-09-16 at 22:27 +0300, Konstantin Belousov wrote: > On Tue, Sep 16, 2014 at 12:08:54PM -0700, Sean Bruno wrote: > > On Tue, 2014-09-16 at 21:57 +0300, Konstantin Belousov wrote: > > > On Tue, Sep 16, 2014 at 11:40:15AM -0700, Sean Bruno wrote: > > > > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > > > > > > > I assume that there is missing error handling in or logic here somewhere > > > > as every one of my machines is spamming my consoles on startup with this > > > > new message. > > > > > > This is after r271493. The hv_kvpd lacks 'NO' entry > > > in the /etc/defaults/rc.conf. > > > > Right, something like this should be added? > Yes, assuming it indeed solves the issue. > > > > > > Index: rc.conf > > === > > --- rc.conf (revision 271679) > > +++ rc.conf (working copy) > > @@ -684,6 +684,8 @@ > > jail_parallel_start="NO" # Start jails in the background > > jail_list="" # Space separated list of names of jails > > > > +hv_kvpd_enable="NO"# Start the Hyper-V key-value Pair Driver > > hv_kvp(4) > > + > > ## > > ### Define source_rc_confs, the mechanism used by /etc/rc.* ## > > ### scripts to source rc_conf_files overrides safely. ## > > Hopefully, I didn't make things worse? https://svnweb.freebsd.org/base?view=revision&revision=271688 sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New spam on all my current machine consoles
On Tue, Sep 16, 2014 at 12:08:54PM -0700, Sean Bruno wrote: > On Tue, 2014-09-16 at 21:57 +0300, Konstantin Belousov wrote: > > On Tue, Sep 16, 2014 at 11:40:15AM -0700, Sean Bruno wrote: > > > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > > > > > I assume that there is missing error handling in or logic here somewhere > > > as every one of my machines is spamming my consoles on startup with this > > > new message. > > > > This is after r271493. The hv_kvpd lacks 'NO' entry > > in the /etc/defaults/rc.conf. > > Right, something like this should be added? Yes, assuming it indeed solves the issue. > > Index: rc.conf > === > --- rc.conf (revision 271679) > +++ rc.conf (working copy) > @@ -684,6 +684,8 @@ > jail_parallel_start="NO" # Start jails in the background > jail_list="" # Space separated list of names of jails > > +hv_kvpd_enable="NO" # Start the Hyper-V key-value Pair Driver hv_kvp(4) > + > ## > ### Define source_rc_confs, the mechanism used by /etc/rc.* ## > ### scripts to source rc_conf_files overrides safely.## > pgpS10wRpPqV6.pgp Description: PGP signature
Re: New spam on all my current machine consoles
On Tue, 2014-09-16 at 21:57 +0300, Konstantin Belousov wrote: > On Tue, Sep 16, 2014 at 11:40:15AM -0700, Sean Bruno wrote: > > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > > > I assume that there is missing error handling in or logic here somewhere > > as every one of my machines is spamming my consoles on startup with this > > new message. > > This is after r271493. The hv_kvpd lacks 'NO' entry > in the /etc/defaults/rc.conf. Right, something like this should be added? Index: rc.conf === --- rc.conf (revision 271679) +++ rc.conf (working copy) @@ -684,6 +684,8 @@ jail_parallel_start="NO" # Start jails in the background jail_list="" # Space separated list of names of jails +hv_kvpd_enable="NO"# Start the Hyper-V key-value Pair Driver hv_kvp(4) + ## ### Define source_rc_confs, the mechanism used by /etc/rc.* ## ### scripts to source rc_conf_files overrides safely. ## ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New spam on all my current machine consoles
On Tue, Sep 16, 2014 at 11:40:15AM -0700, Sean Bruno wrote: > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > I assume that there is missing error handling in or logic here somewhere > as every one of my machines is spamming my consoles on startup with this > new message. This is after r271493. The hv_kvpd lacks 'NO' entry in the /etc/defaults/rc.conf. pgpCZ1eQiGXvD.pgp Description: PGP signature
Re: New spam on all my current machine consoles
On Tue, 2014-09-16 at 11:45 -0700, Garrett Cooper wrote: > > On Sep 16, 2014, at 11:40, Sean Bruno wrote: > > > > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > > > I assume that there is missing error handling in or logic here somewhere > > as every one of my machines is spamming my consoles on startup with this > > new message. > > uname -a? FreeBSD redbuild01.nyi.freebsd.org 11.0-CURRENT FreeBSD 11.0-CURRENT #9 r271631: Mon Sep 15 16:38:04 UTC 2014 sbr...@redbuild01.nyi.freebsd.org:/usr/obj/usr/src/sys/REDBUILD amd64 sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New spam on all my current machine consoles
> On Sep 16, 2014, at 11:40, Sean Bruno wrote: > > HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory > > I assume that there is missing error handling in or logic here somewhere > as every one of my machines is spamming my consoles on startup with this > new message. uname -a? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
New spam on all my current machine consoles
HV_KVP: open /dev/hv_kvp_dev failed; error: 2 No such file or directory I assume that there is missing error handling in or logic here somewhere as every one of my machines is spamming my consoles on startup with this new message. sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Any recent spam that states it is from me is not.
Please check the headers and then ask me. This is for those who may assume that I do such things. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Thu, Dec 26, 2013 at 11:06:34AM -0800, Steve Kargl wrote: > On Thu, Dec 26, 2013 at 12:41:31PM +0100, Baptiste Daroussin wrote: > > On Thu, Dec 26, 2013 at 10:16:44PM +1100, Peter Jeremy wrote: > > > On 2013-Dec-22 11:53:17 -0800, Darren Pilgrim > > > wrote: > > > >Because of that deinstall log. When you use `pkg install` to upgrade a > > > >port, you get something like this: > > > > > > > >Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed > > > >Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 > > > > > > > >That information does not exist in the pkg database. > > > > > > I agree that's a serious bug/regression in the pkg database: With the > > > old pkg system, I could tell when a port was installed by looking at > > > the timestamps on the +COMMENT file. The install time is needed to > > > answer questions like "does this entry in UPDATING affect me" (ie have > > > I rebuilt the port since the entry date). It's something I used > > > regularly and its absence is a PITA. > > > > You can still query from the package database about the installation time. > > > > How? > > % pkg info | grep gcc > gcc-4.6.4 GNU Compiler Collection 4.6 > makedep-1.0.2_1 Create dependencies in makefiles using 'gcc -M' > % pkg query -F gcc-4.6.4 %t > pkg: archive_read_open_filename(gcc-4.6.4): Failed to open 'gcc-4.6.4' > % pkg query %t gcc-4.6.4 > 1387742889 > > Is that seconds since the epoch? If yes, if may be prudent to add a > %T format, so one can easily determine that 1387742889 is Sun Dec 22 > 23:20:51 2013. > Good idea. regards, Bapt pgp_uN6pLRV6n.pgp Description: PGP signature
Re: PACKAGESITE spam
On Thu, Dec 26, 2013 at 12:41:31PM +0100, Baptiste Daroussin wrote: > On Thu, Dec 26, 2013 at 10:16:44PM +1100, Peter Jeremy wrote: > > On 2013-Dec-22 11:53:17 -0800, Darren Pilgrim > > wrote: > > >Because of that deinstall log. When you use `pkg install` to upgrade a > > >port, you get something like this: > > > > > >Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed > > >Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 > > > > > >That information does not exist in the pkg database. > > > > I agree that's a serious bug/regression in the pkg database: With the > > old pkg system, I could tell when a port was installed by looking at > > the timestamps on the +COMMENT file. The install time is needed to > > answer questions like "does this entry in UPDATING affect me" (ie have > > I rebuilt the port since the entry date). It's something I used > > regularly and its absence is a PITA. > > You can still query from the package database about the installation time. > How? % pkg info | grep gcc gcc-4.6.4 GNU Compiler Collection 4.6 makedep-1.0.2_1 Create dependencies in makefiles using 'gcc -M' % pkg query -F gcc-4.6.4 %t pkg: archive_read_open_filename(gcc-4.6.4): Failed to open 'gcc-4.6.4' % pkg query %t gcc-4.6.4 1387742889 Is that seconds since the epoch? If yes, if may be prudent to add a %T format, so one can easily determine that 1387742889 is Sun Dec 22 23:20:51 2013. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Thu, Dec 26, 2013 at 10:16:44PM +1100, Peter Jeremy wrote: > On 2013-Dec-22 11:53:17 -0800, Darren Pilgrim > wrote: > >Because of that deinstall log. When you use `pkg install` to upgrade a > >port, you get something like this: > > > >Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed > >Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 > > > >That information does not exist in the pkg database. > > I agree that's a serious bug/regression in the pkg database: With the > old pkg system, I could tell when a port was installed by looking at > the timestamps on the +COMMENT file. The install time is needed to > answer questions like "does this entry in UPDATING affect me" (ie have > I rebuilt the port since the entry date). It's something I used > regularly and its absence is a PITA. You can still query from the package database about the installation time. With the ancient system you had no way to determine if something was reinstalled You add no way to determine if it was an upgrade You add no way to fihure out what something was removed. > > I shouldn't need to rummage through /var/log/messages - and in any case, > by default FreeBSD only keeps 500K of messages history (about a month > in my case) so the information has probably rotated into the bit bucket. > > I agree that having a pkg audit trail would be useful. Unfortunately, > what we have today is not an audit trail and isn't especially useful. it is an audit trail, it is very useful in lots of cases as I spotted before, and it is also mandatory for some security certification in that form precisely. You want other cases, here is 2 others very very usual cases? Determine what has been done when managing a farm of servers with puppet,cfengine,salt,anssible and friens. Determine what has been done when you have multiple admins on your servers regards, Bapt pgpKZRI3knk4r.pgp Description: PGP signature
Re: PACKAGESITE spam
On 2013-Dec-22 11:53:17 -0800, Darren Pilgrim wrote: >Because of that deinstall log. When you use `pkg install` to upgrade a >port, you get something like this: > >Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed >Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 > >That information does not exist in the pkg database. I agree that's a serious bug/regression in the pkg database: With the old pkg system, I could tell when a port was installed by looking at the timestamps on the +COMMENT file. The install time is needed to answer questions like "does this entry in UPDATING affect me" (ie have I rebuilt the port since the entry date). It's something I used regularly and its absence is a PITA. I shouldn't need to rummage through /var/log/messages - and in any case, by default FreeBSD only keeps 500K of messages history (about a month in my case) so the information has probably rotated into the bit bucket. I agree that having a pkg audit trail would be useful. Unfortunately, what we have today is not an audit trail and isn't especially useful. -- Peter Jeremy pgpVS_m9BxiAC.pgp Description: PGP signature
Re: PACKAGESITE spam
On 12/22/2013 6:00 AM, Frank Seltzer wrote: Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. There are two more: 1. When a port was deinstalled 2. History of a port (previous installs/deinstalls) For example, my logs have: Sep 9 16:05:28 chombo pkg-static: postfix-2.10.0,1 deinstalled Sep 9 16:05:36 chombo pkg-static: postfix-2.10.0,1 installed Nov 30 00:25:02 chombo pkg: postfix-2.10.0,1 deinstalled Nov 30 00:25:09 chombo pkg-static: postfix-2.10.2,1 installed Which tells me I recompiled postfix on Sept 9 (this would have been when I changed it over to openssl from ports) and updated it to 2.10.2 on Nov 30 using portmaster. How do I know that? Because of that deinstall log. When you use `pkg install` to upgrade a port, you get something like this: Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 That information does not exist in the pkg database. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? I have never understood why anyone would enable the use of syslog without also providing a way of specifying the facility and level. I'd much rather do stuff like this: local0.*/var/log/dovecot.log local1.*/var/log/postgres.log local2.*/var/log/php-fpm.log ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
Frank Seltzer wrote, On 12/22/2013 15:00: Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. All of this is mostly off-topic. I haven't had any opposition to logging. Instead, I originally thought that the PACKAGESITE spam was a result of a bug, because -- the spam appeared with a recent installworld; -- there were like 50 consecutive messages every now and then; -- I don't recall ever setting up any PACKAGESITE-related variables (the timestamp on the file is 2013-04-05, so I could be WRONG); -- I looked for pkg.conf (only) in /etc, and didn't find it there; -- neither of the UPDATING files contain instructions regarding pkg.conf; -- I haven't payed too much attention to HEADSUP mails in the last few weeks (what relevant things did I miss?). Why is pkg.conf in /usr/local/etc instead of /etc? By contrast, why does the sample configuration file (/usr/local/etc/pkg.conf.sample) contain a line that links to a file in /etc, namely "#PUBKEY : /etc/ssl/pkg.conf"? The pkg.conf of a -RELEASE won't be as "empty" as mine is currently (causing PACKAGESITE spam), will it? If not (obviously), then what will it look like? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sun, 22 Dec 2013 15:48:49 +0400, Gleb Smirnoff wrote: > Steve, > > On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S> It did > not ask how to stop this stupidity. I asked to have S> this stupidity > stopped by default. The spewing of this S> information in > /var/log/messages provides NOTHING. Please S> turn it off by default. > > I am really suprised that someone might want to see this off by default. I concur. pkg info provides details of *currently installed* packages, whereas the information in syslog yields a *history*. This arrangement seems eminently reasonable to me. It all seems a bit of a storm in a teacup anyway, given that the logging can be directed to another file or turned off altogether, depending on requirements. My vote: Maintainers, thanks for your efforts and please keep it as it is. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sun, 22 Dec 2013, Baptiste Daroussin wrote: On Sun, Dec 22, 2013 at 09:00:42AM -0500, Frank Seltzer wrote: /root # man pkg.conf No manual entry for pkg.conf pkg.conf man pages comes with pkg itself, just bootstrap it and you will get the manpage :) regards, Bapt OK, my bad, I did this on a 9.2-STABLE system by mistake. This question still stands. Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, 2013-12-21 at 15:25 -0800, Steve Kargl wrote: > On Sun, Dec 22, 2013 at 12:16:00AM +0100, Julien Laffaye wrote: > > On 12/22/2013 12:04 AM, Steve Kargl wrote: > > > On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: > > >> this has been done and activated for reason, first for lot of companies, > > > companies can turn it on it they want it. > > > > And if you want to save the few extra kB, you can turn it off... > > I have turned it off. > > > >> secondly I receive tons of request to actiavte on by default while > > >> you are the first to request it off by default > > > I certainly can't refute 'tons of [private] requests'. There is > > > no discussing of such logging in freebsd-current, freebsd-hackers, > > > or freebsd-ports lists. > > > > > > Other than the noise in /var/log/message, what does this provide > > > that 'pkg info' doesn't! Please turn of this feature by default. > > > > > > > Actually, you are the one making noise... > > What does this logging in /var/log/message provide that is > not provided by 'pkg info'? It is useless noise. > "Useless noise" is what you get when someone holds an opinion that clearly nobody else agrees with, and yet they somehow think that just saying it over and over again will change peoples' minds. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 22/12/2013 16:08, Matthew Seaman wrote: > On 22/12/2013 14:55, olli hauer wrote: >> What I agree is having it would be nice to have dedicated syslog >> (like yum.log) instead /var/log/messages since this is already >> spammed by most every process. > > Add something like this to /etc/syslog.conf: > > !pkg > *.* /var/log/pkg.log ... although, yes, it's a bit archaic that there are as standard LOG_UUCP and LOG_NEWS facilities in syslog(3) -- neither of which are much used nowadays -- while there is only the generic LOG_DAEMON for things like webservers, LDAP, XMPP, PPP and many other network services, and nothing at all for system maintenance type things like updating packages. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: PACKAGESITE spam
On 22/12/2013 14:55, olli hauer wrote: > What I agree is having it would be nice to have dedicated syslog > (like yum.log) instead /var/log/messages since this is already > spammed by most every process. Add something like this to /etc/syslog.conf: !pkg *.* /var/log/pkg.log Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: PACKAGESITE spam
On 2013-12-22 15:00, Frank Seltzer wrote: > > On Sat, 21 Dec 2013, Steve Kargl wrote: > >> On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: >>> I've just installed a very recent -CURRENT, and now I'm performing a big >>> portupgrade procedure. I get the following message spammed a lot: >>> >>> pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository >>> configuration file >> >> Yeah, I noticed that spam along with the spam that is being >> spewed to /var/log/messaage, e.g., >> >> Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed >> Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed >> Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed >> Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed >> Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed >> Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed >> Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed >> Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed >> Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed >> >> Can you (portmgr) please mute these messages? >> >> -- >> Steve > > This received several responses. > > Greg Rivers said: > > Do you really feel that strongly about it? Having a record of changes to > the system has always seemed like a feature to me... > > Baptiste Daroussin said: > > this has been done and activated for reason, first for lot of companies, it > is important (PCI DSS requirement for example), secondly I receive tons of > request to actiavte on by default while you are the first to request it off > by default > > Adrian Chadd said: > > The point is that some people like an audit trail. The audit trail for > some people involves remote logging of syslog messages to a log host. > This would include when packages are installed. > > My thought: > > Then why can't the messages about installed ports have it's own log file > rather than /var/log/messages? > > As for this message: > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > configuration file > > Glen Barber replied: > > echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf > > And Shane Ambler: > > now we can turn it off which I don't think we could before. > > Me again: > > Where is this documented? > > /root # man pkg.conf > No manual entry for pkg.conf Hm, on all my systems I have a man page for pkg.conf Here is the referenced passage from man 5 pkg.conf OPTIONS The following options can be defined in pkg.conf: ... SYSLOG: booleanThis option is enabled by default, log all the installation/deinstallation/upgrade oper- ation via syslog(3) What I agree is having it would be nice to have dedicated syslog (like yum.log) instead /var/log/messages since this is already spammed by most every process. -- olli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sun, Dec 22, 2013 at 09:00:42AM -0500, Frank Seltzer wrote: > > On Sat, 21 Dec 2013, Steve Kargl wrote: > > > On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: > >> I've just installed a very recent -CURRENT, and now I'm performing a > >> big portupgrade procedure. I get the following message spammed a lot: > >> > >> pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > >> configuration file > > > > Yeah, I noticed that spam along with the spam that is being > > spewed to /var/log/messaage, e.g., > > > > Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed > > Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed > > Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed > > Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed > > Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed > > Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed > > Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed > > Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed > > Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed > > > > Can you (portmgr) please mute these messages? > > > > -- > > Steve > > This received several responses. > > Greg Rivers said: > > Do you really feel that strongly about it? Having a record of changes to > the system has always seemed like a feature to me... > > Baptiste Daroussin said: > > this has been done and activated for reason, first for lot of companies, > it is important (PCI DSS requirement for example), secondly I receive tons > of request to actiavte on by default while you are the first to request it > off by default > > Adrian Chadd said: > > The point is that some people like an audit trail. The audit trail for > some people involves remote logging of syslog messages to a log host. > This would include when packages are installed. > > My thought: > > Then why can't the messages about installed ports have it's own log file > rather than /var/log/messages? > > As for this message: > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > configuration file > > Glen Barber replied: > > echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf > > And Shane Ambler: > > now we can turn it off which I don't think we could before. > > Me again: > > Where is this documented? > > /root # man pkg.conf > No manual entry for pkg.conf pkg.conf man pages comes with pkg itself, just bootstrap it and you will get the manpage :) regards, Bapt pgppN2wGUhy2L.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, 21 Dec 2013, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? -- Steve This received several responses. Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. Me again: Where is this documented? /root # man pkg.conf No manual entry for pkg.conf ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
Steve, On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S> It did not ask how to stop this stupidity. I asked to have S> this stupidity stopped by default. The spewing of this S> information in /var/log/messages provides NOTHING. Please S> turn it off by default. I am really suprised that someone might want to see this off by default. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. -adrian On 21 December 2013 15:49, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 06:47:01PM -0500, Glen Barber wrote: >> On Sat, Dec 21, 2013 at 03:44:11PM -0800, Steve Kargl wrote: >> > On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: >> > > In article <20131221230448.ga61...@troutmask.apl.washington.edu>, >> > > Steve Kargl writes: >> > > >> > > >Other than the noise in /var/log/message, what does this provide >> > > >that 'pkg info' doesn't! >> > > >> > > A record of when packages were installed and removed. >> > > >> > >> > The date/time a package is installed should be recorded >> > in the pkg database and be available with 'pkg info -f'. >> > Of course, it appeat that this information s not properly >> > recorded. >> > >> >> Because databases are never corruptible? >> > > /var/log/message never gets corrupted? > > -- > Steve > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 22/12/2013 09:34, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: >> >> this has been done and activated for reason, first for lot of companies, > > companies can turn it on it they want it. Generally the more secure option is default, you can turn off security options as you choose. >> secondly I receive tons of request to actiavte on by default while >> you are the first to request it off by default > > I certainly can't refute 'tons of [private] requests'. There is > no discussing of such logging in freebsd-current, freebsd-hackers, > or freebsd-ports lists. > > Other than the noise in /var/log/message, what does this provide > that 'pkg info' doesn't! Please turn of this feature by default. > Isn't this "noise" the same as we had with the old package system? So really nothing has changed, well now we can turn it off which I don't think we could before. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
I was surprised initially, but haven't thought about it much since. -- View this message in context: http://freebsd.1045724.n5.nabble.com/PACKAGESITE-spam-tp5870583p5870666.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
In article <20131221230448.ga61...@troutmask.apl.washington.edu>, Steve Kargl writes: >Other than the noise in /var/log/message, what does this provide >that 'pkg info' doesn't! A record of when packages were installed and removed. -GAWollman ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 03:49:26PM -0800, Steve Kargl wrote: > /var/log/message never gets corrupted? > If a machine is compromised, I can review log from remote syslog server. It is impossible to trust the package information, relying on the local database alone. Glen pgpklyEF3RMKl.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 03:44:11PM -0800, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: > > In article <20131221230448.ga61...@troutmask.apl.washington.edu>, > > Steve Kargl writes: > > > > >Other than the noise in /var/log/message, what does this provide > > >that 'pkg info' doesn't! > > > > A record of when packages were installed and removed. > > > > The date/time a package is installed should be recorded > in the pkg database and be available with 'pkg info -f'. > Of course, it appeat that this information s not properly > recorded. > > -- > Steve > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Works for installation and we do track it, does not work for removal seriously are installing that many packages everyday that it bother you? regards, Bapt pgpe1334kYS1T.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 06:47:01PM -0500, Glen Barber wrote: > On Sat, Dec 21, 2013 at 03:44:11PM -0800, Steve Kargl wrote: > > On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: > > > In article <20131221230448.ga61...@troutmask.apl.washington.edu>, > > > Steve Kargl writes: > > > > > > >Other than the noise in /var/log/message, what does this provide > > > >that 'pkg info' doesn't! > > > > > > A record of when packages were installed and removed. > > > > > > > The date/time a package is installed should be recorded > > in the pkg database and be available with 'pkg info -f'. > > Of course, it appeat that this information s not properly > > recorded. > > > > Because databases are never corruptible? > /var/log/message never gets corrupted? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 03:44:11PM -0800, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: > > In article <20131221230448.ga61...@troutmask.apl.washington.edu>, > > Steve Kargl writes: > > > > >Other than the noise in /var/log/message, what does this provide > > >that 'pkg info' doesn't! > > > > A record of when packages were installed and removed. > > > > The date/time a package is installed should be recorded > in the pkg database and be available with 'pkg info -f'. > Of course, it appeat that this information s not properly > recorded. > Because databases are never corruptible? Glen pgplQ34lUTbQB.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: > In article <20131221230448.ga61...@troutmask.apl.washington.edu>, > Steve Kargl writes: > > >Other than the noise in /var/log/message, what does this provide > >that 'pkg info' doesn't! > > A record of when packages were installed and removed. > The date/time a package is installed should be recorded in the pkg database and be available with 'pkg info -f'. Of course, it appeat that this information s not properly recorded. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 22/12/13 00:04, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: >> > > Other than the noise in /var/log/message, what does this provide > that 'pkg info' doesn't! Please turn of this feature by default. > No please don't, it's a very useful feature, you can see when packages were installed or upgraded. Which can be very useful in certain environments. Additionally, looking at other systems (SLES, CentOS, Debian and Ubuntu from the top of my head) they all have a log that keeps track of packages. The idea cannot be *that* useless. Florian signature.asc Description: OpenPGP digital signature
Re: PACKAGESITE spam
On 12/22/2013 12:25 AM, Steve Kargl wrote: On Sun, Dec 22, 2013 at 12:16:00AM +0100, Julien Laffaye wrote: On 12/22/2013 12:04 AM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. And if you want to save the few extra kB, you can turn it off... I have turned it off. secondly I receive tons of request to actiavte on by default while you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. Actually, you are the one making noise... What does this logging in /var/log/message provide that is not provided by 'pkg info'? It is useless noise. Forensics ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sun, Dec 22, 2013 at 12:16:00AM +0100, Julien Laffaye wrote: > On 12/22/2013 12:04 AM, Steve Kargl wrote: > > On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: > >> this has been done and activated for reason, first for lot of companies, > > companies can turn it on it they want it. > > And if you want to save the few extra kB, you can turn it off... I have turned it off. > >> secondly I receive tons of request to actiavte on by default while > >> you are the first to request it off by default > > I certainly can't refute 'tons of [private] requests'. There is > > no discussing of such logging in freebsd-current, freebsd-hackers, > > or freebsd-ports lists. > > > > Other than the noise in /var/log/message, what does this provide > > that 'pkg info' doesn't! Please turn of this feature by default. > > > > Actually, you are the one making noise... What does this logging in /var/log/message provide that is not provided by 'pkg info'? It is useless noise. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 12/22/2013 12:04 AM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. And if you want to save the few extra kB, you can turn it off... secondly I receive tons of request to actiavte on by default while you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. Actually, you are the one making noise... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: > > this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. > secondly I receive tons of request to actiavte on by default while > you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 01:39:59PM -0800, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 01:24:55PM -0800, Darren Pilgrim wrote: > > On 12/21/2013 1:05 PM, Steve Kargl wrote: > > > On Sat, Dec 21, 2013 at 02:54:39PM -0600, Greg Rivers wrote: > > >> On Sat, 21 Dec 2013, Steve Kargl wrote: > > >> > > >>> It did not ask how to stop this stupidity. I asked to have this > > >>> stupidity stopped by default. The spewing of this information in > > >>> /var/log/messages provides NOTHING. Please turn it off by default. > > >>> > > >> > > >> Do you really feel that strongly about it? Having a record of changes to > > >> the system has always seemed like a feature to me... > > >> > > > > > > Yes, I do feel strongly about it. It is completely unnecesary noise. > > > It should be off by default. If someone wants to fill /var up with > > > useless information, then that someone can turn on the noise. > > > > It's about what's safe in the common case. There are significant > > security risks inherent in pkg's activities, so having a written > > external record is the safe option. > > > > I don't buy the "fill up /var" argument. If your /var is so small that > > pkg's logging risks filling it up, why are you not logging to an > > external syslog server? There are much more voluminous sources of logs > > on a FreeBSD system. > > It has nothing to do with the size of /var, really. It is completely > useless information. You want to know what package are installed, use > 'pkg info'. Packages do not spontaneously install themselves. If > your system is so insecure that you are worried that some unpriveleged > user installed a package, you have bigger problems. > > -- > steve > > > -- > Steve > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Bapt pgpuaUQdFoTIm.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 01:24:55PM -0800, Darren Pilgrim wrote: > On 12/21/2013 1:05 PM, Steve Kargl wrote: > > On Sat, Dec 21, 2013 at 02:54:39PM -0600, Greg Rivers wrote: > >> On Sat, 21 Dec 2013, Steve Kargl wrote: > >> > >>> It did not ask how to stop this stupidity. I asked to have this > >>> stupidity stopped by default. The spewing of this information in > >>> /var/log/messages provides NOTHING. Please turn it off by default. > >>> > >> > >> Do you really feel that strongly about it? Having a record of changes to > >> the system has always seemed like a feature to me... > >> > > > > Yes, I do feel strongly about it. It is completely unnecesary noise. > > It should be off by default. If someone wants to fill /var up with > > useless information, then that someone can turn on the noise. > > It's about what's safe in the common case. There are significant > security risks inherent in pkg's activities, so having a written > external record is the safe option. > > I don't buy the "fill up /var" argument. If your /var is so small that > pkg's logging risks filling it up, why are you not logging to an > external syslog server? There are much more voluminous sources of logs > on a FreeBSD system. It has nothing to do with the size of /var, really. It is completely useless information. You want to know what package are installed, use 'pkg info'. Packages do not spontaneously install themselves. If your system is so insecure that you are worried that some unpriveleged user installed a package, you have bigger problems. -- steve -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 12/21/2013 1:05 PM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 02:54:39PM -0600, Greg Rivers wrote: On Sat, 21 Dec 2013, Steve Kargl wrote: It did not ask how to stop this stupidity. I asked to have this stupidity stopped by default. The spewing of this information in /var/log/messages provides NOTHING. Please turn it off by default. Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Yes, I do feel strongly about it. It is completely unnecesary noise. It should be off by default. If someone wants to fill /var up with useless information, then that someone can turn on the noise. It's about what's safe in the common case. There are significant security risks inherent in pkg's activities, so having a written external record is the safe option. I don't buy the "fill up /var" argument. If your /var is so small that pkg's logging risks filling it up, why are you not logging to an external syslog server? There are much more voluminous sources of logs on a FreeBSD system. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 02:54:39PM -0600, Greg Rivers wrote: > On Sat, 21 Dec 2013, Steve Kargl wrote: > > > It did not ask how to stop this stupidity. I asked to have this > > stupidity stopped by default. The spewing of this information in > > /var/log/messages provides NOTHING. Please turn it off by default. > > > > Do you really feel that strongly about it? Having a record of changes to > the system has always seemed like a feature to me... > Yes, I do feel strongly about it. It is completely unnecesary noise. It should be off by default. If someone wants to fill /var up with useless information, then that someone can turn on the noise. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, 21 Dec 2013, Steve Kargl wrote: On Sat, Dec 21, 2013 at 03:10:26PM -0500, Glen Barber wrote: On Sat, Dec 21, 2013 at 12:05:38PM -0800, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf It did not ask how to stop this stupidity. I asked to have this stupidity stopped by default. The spewing of this information in /var/log/messages provides NOTHING. Please turn it off by default. Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... -- Greg ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On 12/21/2013 9:14 PM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 03:10:26PM -0500, Glen Barber wrote: On Sat, Dec 21, 2013 at 12:05:38PM -0800, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf It did not ask how to stop this stupidity. I asked to have this stupidity stopped by default. The spewing of this information in /var/log/messages provides NOTHING. Please turn it off by default. Obviously, if it is on by default, others have different opinions on this subject... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 03:10:26PM -0500, Glen Barber wrote: > On Sat, Dec 21, 2013 at 12:05:38PM -0800, Steve Kargl wrote: > > On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: > > > I've just installed a very recent -CURRENT, and now I'm performing a big > > > portupgrade procedure. I get the following message spammed a lot: > > > > > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > > > configuration file > > > > Yeah, I noticed that spam along with the spam that is being > > spewed to /var/log/messaage, e.g., > > > > Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed > > Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed > > Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed > > Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed > > > > Can you (portmgr) please mute these messages? > > > > echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf > It did not ask how to stop this stupidity. I asked to have this stupidity stopped by default. The spewing of this information in /var/log/messages provides NOTHING. Please turn it off by default. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 12:05:38PM -0800, Steve Kargl wrote: > On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: > > I've just installed a very recent -CURRENT, and now I'm performing a big > > portupgrade procedure. I get the following message spammed a lot: > > > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > > configuration file > > Yeah, I noticed that spam along with the spam that is being > spewed to /var/log/messaage, e.g., > > Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed > Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed > Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed > Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed > Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed > Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed > Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed > Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed > Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed > > Can you (portmgr) please mute these messages? > echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf Glen pgpcL2CgmtLq7.pgp Description: PGP signature
Re: PACKAGESITE spam
On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: > I've just installed a very recent -CURRENT, and now I'm performing a big > portupgrade procedure. I get the following message spammed a lot: > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository > configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PACKAGESITE spam
I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
On Thu, 2012-10-04 at 22:24 +0200, Marek Salwerowicz wrote: > W dniu 2012-10-04 20:51, Lev Serebryakov pisze: > > Hello, Marek. > > You wrote 3 октября 2012 г., 23:17:35: > > > >>> atrtc0: port 0x70-0x71 on acpi0 > > MS> still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host > > MS> Do you have any solution? > > In my case it was local patch for exotic embedded chipset... > Can you send me the patch so I can have a look if I don't use the same > chipset ? > > Regards, It is the patch attached to this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=170705 The patch fixes a problem with old AMD Geode chipsets, but causes a hang at atrtc attach when run under virtualbox, and I haven't had time yet to install and learn to use vbox enough to debug it. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection
W dniu 2012-10-04 20:51, Lev Serebryakov pisze: Hello, Marek. You wrote 3 октября 2012 г., 23:17:35: atrtc0: port 0x70-0x71 on acpi0 MS> still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host MS> Do you have any solution? In my case it was local patch for exotic embedded chipset... Can you send me the patch so I can have a look if I don't use the same chipset ? Regards, -- Marek Salwerowicz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [maybe spam] Re: running old binaries on -current
On Sun, 04 Dec 2011 13:56:11 -0800 Julian Elischer wrote: > On 12/4/11 12:30 PM, Yamagi Burmeister wrote: > > On Sun, 4 Dec 2011 22:25:19 +0200 > > Kostik Belousov wrote: > > > >> Try to set sysctl security.bsd.map_at_zero to 1. > > I didn't even think of that. It helped, thanks :) > > > do you have a full 1.0 iso image somewhere? (or a copy of hte release?) >I had a 1.1 cd but I can not find it now. For some time now iso images of those acient releases and even some development snapshots can be found in the ftp archiv: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ISO-IMAGES My iso images were taken direcly from cds found in the library of the department for computer science at the local university. The file size is the same as of those in the ftp archive. -- Homepage: www.yamagi.org XMPP: yam...@yamagi.org GnuPG/GPG: 0xEFBCCBCB pgpVSezRNJGBE.pgp Description: PGP signature
Re: Console Spam: acpi_tz0: _TMP value is absurd, ignored (-73.0C) [solved]
On Wed, 2011-11-30 at 15:55 -0800, Jung-uk Kim wrote: > On Wednesday 30 November 2011 06:40 pm, Andriy Gapon wrote: > > on 01/12/2011 01:22 Sean Bruno said the following: > > > I have a Shuttle based intel box that appears to have some pretty > > > bad ACPI implementation. Is there a good way to quiesce this > > > spam? > > > > Ask on acpi@ list. > > Kidding :-) or not. > > Try hw.acpi.thermal.polling_rate=0. > > Adding the following line in /boot/loader.conf will disable > acpi_thermal(4) completely: > > debug.acpi.disabled="thermal" > > Jung-uk Kim Aye, both are my "huckleberry". Thanks! Sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Console Spam: acpi_tz0: _TMP value is absurd, ignored (-73.0C)
On Wednesday 30 November 2011 06:40 pm, Andriy Gapon wrote: > on 01/12/2011 01:22 Sean Bruno said the following: > > I have a Shuttle based intel box that appears to have some pretty > > bad ACPI implementation. Is there a good way to quiesce this > > spam? > > Ask on acpi@ list. > Kidding :-) or not. > Try hw.acpi.thermal.polling_rate=0. Adding the following line in /boot/loader.conf will disable acpi_thermal(4) completely: debug.acpi.disabled="thermal" Jung-uk Kim > > The console fills up with repeated warnings that never cease. > > FreeBSD testbox 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r228164S: > > Wed Nov 30 16:19:16 PST 2011 > > sbruno@testbox:/tmp/foo/bsd/head/sys/GENERIC_NO_1394 amd64 > > > > [sbruno@testbox ~]$ sysctl -a |grep thermal > > "Giant","ACPI thermal zone" > > hw.acpi.thermal.min_runtime: 0 > > hw.acpi.thermal.polling_rate: 10 > > hw.acpi.thermal.user_override: 0 > > hw.acpi.thermal.tz0.temperature: -273.2C > > hw.acpi.thermal.tz0.active: -2 > > hw.acpi.thermal.tz0.passive_cooling: 1 > > hw.acpi.thermal.tz0.thermal_flags: 0 > > hw.acpi.thermal.tz0._PSV: 50.0C > > hw.acpi.thermal.tz0._HOT: -1 > > hw.acpi.thermal.tz0._CRT: 60.0C > > hw.acpi.thermal.tz0._ACx: 50.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 > > hw.acpi.thermal.tz0._TC1: 4 > > hw.acpi.thermal.tz0._TC2: 3 > > hw.acpi.thermal.tz0._TSP: 60 > > ... > > dev.acpi_tz.0.%desc: Thermal Zone > > dev.acpi_tz.0.%driver: acpi_tz > > dev.acpi_tz.0.%location: handle=\_TZ_.THRM > > dev.acpi_tz.0.%pnpinfo: _HID=none _UID=0 > > dev.acpi_tz.0.%parent: acpi0 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Console Spam: acpi_tz0: _TMP value is absurd, ignored (-73.0C)
on 01/12/2011 01:22 Sean Bruno said the following: > I have a Shuttle based intel box that appears to have some pretty bad > ACPI implementation. Is there a good way to quiesce this spam? Ask on acpi@ list. Kidding :-) or not. Try hw.acpi.thermal.polling_rate=0. > The console fills up with repeated warnings that never cease. > FreeBSD testbox 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r228164S: Wed Nov > 30 16:19:16 PST 2011 > sbruno@testbox:/tmp/foo/bsd/head/sys/GENERIC_NO_1394 amd64 > > [sbruno@testbox ~]$ sysctl -a |grep thermal > "Giant","ACPI thermal zone" > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: -273.2C > hw.acpi.thermal.tz0.active: -2 > hw.acpi.thermal.tz0.passive_cooling: 1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 50.0C > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 60.0C > hw.acpi.thermal.tz0._ACx: 50.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: 4 > hw.acpi.thermal.tz0._TC2: 3 > hw.acpi.thermal.tz0._TSP: 60 > ... > dev.acpi_tz.0.%desc: Thermal Zone > dev.acpi_tz.0.%driver: acpi_tz > dev.acpi_tz.0.%location: handle=\_TZ_.THRM > dev.acpi_tz.0.%pnpinfo: _HID=none _UID=0 > dev.acpi_tz.0.%parent: acpi0 -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Console Spam: acpi_tz0: _TMP value is absurd, ignored (-73.0C)
I have a Shuttle based intel box that appears to have some pretty bad ACPI implementation. Is there a good way to quiesce this spam? The console fills up with repeated warnings that never cease. FreeBSD testbox 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r228164S: Wed Nov 30 16:19:16 PST 2011 sbruno@testbox:/tmp/foo/bsd/head/sys/GENERIC_NO_1394 amd64 [sbruno@testbox ~]$ sysctl -a |grep thermal "Giant","ACPI thermal zone" hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: -273.2C hw.acpi.thermal.tz0.active: -2 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 50.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 60.0C hw.acpi.thermal.tz0._ACx: 50.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: 4 hw.acpi.thermal.tz0._TC2: 3 hw.acpi.thermal.tz0._TSP: 60 ... dev.acpi_tz.0.%desc: Thermal Zone dev.acpi_tz.0.%driver: acpi_tz dev.acpi_tz.0.%location: handle=\_TZ_.THRM dev.acpi_tz.0.%pnpinfo: _HID=none _UID=0 dev.acpi_tz.0.%parent: acpi0 Sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: (CTRL-C to abort) console spam
Hi all, On 12/28/10 07:37, Colin Percival wrote: > The '(CTRL-C to abort)' which gets printed while dumping is irritating me > because EC2's console has a very limited buffer and having this spammed > makes it impossible to see any printfs immediately prior. Never mind, I've had pointed out to me that the '(CTRL-C to abort)' is only printed when there's console input, and I've found a bug in the Xen console code which explains why FreeBSD was thinking that there was input. Move along, nothing to see here. :-) -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
(CTRL-C to abort) console spam
Hi all, The '(CTRL-C to abort)' which gets printed while dumping is irritating me because EC2's console has a very limited buffer and having this spammed makes it impossible to see any printfs immediately prior. (Turning off dumping solves the problem, but creates a worse problem, namely a lack of dumps.) I'd like to add a sysctl to optionally disable this message, with a default behaviour of printing the message. Two questions for the list: 1. Any objections to adding such a sysctl? 2. What colour should the sysctl^W^W^W^W name should the sysctl be given? I'm leaning towards debug.quietdump, but it's not a strong preference. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [SPAM] freebsd-current Digest, Vol 367, Issue 6
--Best Regards,Littlecho This message has been scanned for viruses and dangerous content and is believed to be clean. > Original Message >From: freebsd-current-requ...@freebsd.org >To: freebsd-current@freebsd.org >Sent: Thu, Oct 28, 2010, 20:01 PM >Subject: [SPAM] freebsd-current Digest, Vol 367, Issue 6 > >Send freebsd-current mailing list submissions to > freebsd-current@freebsd.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-current >or, via email, send a message with subject or body 'help' to > freebsd-current-requ...@freebsd.org > >You can reach the person managing the list at > freebsd-current-ow...@freebsd.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of freebsd-current digest..." > > >Today's Topics: > > 1. Re: Broadcom BCM4310 USB Controller (Wifi) (Matthias Apitz) > 2. Re: Broadcom BCM4310 USB Controller (Wifi) (Matthias Apitz) > 3. Re: Broadcom BCM4310 USB Controller (Wifi) (Matthias Apitz) > > >-- > >Message: 1 >Date: Wed, 27 Oct 2010 19:23:48 +0200 >From: Matthias Apitz >Subject: Re: Broadcom BCM4310 USB Controller (Wifi) >To: Alberto Villa >Cc: Scot Hetzel , curr...@freebsd.org >Message-ID: <20101027172348.ga1...@tiny.sisis.de> >Content-Type: text/plain; charset=iso-8859-1 > >El d燰 Wednesday, October 27, 2010 a las 05:10:32PM +, Alberto Villa >escribi: > >> On Wed, Oct 27, 2010 at 5:07 PM, Scot Hetzel wrote: >> > Where did you get your bcmwl5 driver? If you downloaded it from Acer, >> > it should work. If you downloaded it from anywhere else then this >> > might be why it didn't work for you. >> >> i don't remember, actually. anyway i thought the 5 was the driver >> version, i've just understood that it's the windows version :P >> i'll try the acer one, thanks for the suggestion! > >I could no get any bcmwl5 driver from Acer, only bcmwl6 version (which >is also installed in Win7 in my laptop). I have even asked Broadcom, but >they pointed me back to my dealer, to the reseller of the Acer laptop. >And asking them, they pointed to Acer. If someone has an bcmwl5 from >Acer, please contact me off-list. > > matthias >-- >Matthias Apitz >t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 >e - w http://www.unixarea.de/ > > >-- > >Message: 2 >Date: Thu, 28 Oct 2010 08:06:10 +0200 >From: Matthias Apitz >Subject: Re: Broadcom BCM4310 USB Controller (Wifi) >To: Scot Hetzel >Cc: Alberto Villa , curr...@freebsd.org >Message-ID: <20101028060610.gb1...@current.sisis.de> >Content-Type: text/plain; charset=iso-8859-1 > >El d燰 Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel escribi: > >> > Where did you get your bcmwl5 driver? If you downloaded it from Acer, >> > it should work. If you downloaded it from anywhere else then this >> > might be why it didn't work for you. >> > >> >> Just noticed that you didn't specify your computer manufacture. The >> above would only work for Matthias Apitz. >> >> You just need to download the driver from the manufacture of your computer. > >Why is this? Isn't it just the Wifi chip which matters? Could you sheet >a bit light on this? Thanks > > matthias >-- >Matthias Apitz >t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 >e - w http://www.unixarea.de/ > > >-- > >Message: 3 >Date: Thu, 28 Oct 2010 08:32:55 +0200 >From: Matthias Apitz >Subject: Re: Broadcom BCM4310 USB Controller (Wifi) >To: Scot Hetzel >Cc: Alberto Villa , curr...@freebsd.org >Message-ID: <20101028063255.ga17...@current.sisis.de> >Content-Type: text/plain; charset=iso-8859-1 > >El d燰 Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribi: > >> On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote: >> > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote: >> >> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 >> >> driver. Note 5 vs 6 in driver name. >> >> Editing inf files will give you nothing. >> > >> > i've tried that driver, but apparently it doesn't support my card... >> > loading the .ko doesn't show anything... >> >> Where did you get your bcmwl5 driver? If you downloaded it from Acer, >> it should work. If you downloaded it from anywh
Re: [SPAM] Re: Error message while updating src for FreeBSD 9 current
Niclas Zeising wrote: On 2010-09-23 14:02, Bartosz Stec wrote: On 2010-09-23 13:36, Niclas Zeising wrote: On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the following error message when I do a src update. cvsup srcsupfile Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Edit src/bin/ps/extern.h Illegal instruction I am new to the mailing list. Is this a known error? Is this an error to do with the source tree or an issue on my end? Just for reference, the contents of my supfile are *default tag=. *default host=cvsup2.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress src-all ports-all doc-all Thanks in advance for your assistance, Ralph Ellis ralphell...@netscape.ca Are you using cvsup or csup? Have you recompiled cvsup in case you use that? What's in your make.conf file? Illegal instruction is usually because the program is compiled for another CPU than what it's running on. It can also be that syscalls has changed, but then it usually complains about that. When doing a major version upgrade, you usually have to recompile all ports. Hope this helps! //Niclas I am using cvsup. I had recompiled my VirtualBox port but I had not finished recompiling the other major ports. Thanks for the suggestion. My make.conf is deliberately very plain jane with no special conditions or comments. Thanks Ralph Ellis ralphell...@netscape.ca Try to recompile everything, or at least cvsup, and see if it works. //Niclas Niclas, did you perform 'make delete-old && make delete-old-libs' after upgrade to CURRENT? If you did, many of your ports won't longer work properly (or at all) because of missing libraries. If you didn't, you definitely should do something like 'portupgrade -afrRi' and after you done, you can get rid of these old files with commands above. You wouldn't get illegal instruction then though. Usually the application fails to load if dynamic libraries are missing. Of course it could take VERY long time depending on installed ports and machine spec., so if you just need to get your sources updated quickly I recommend: 1. Try csup instead of cvsup. It's integrated in both 8.x and in CURRENT, so should work "out of the box" That's a good idea. 2. If you (for some strange reasons) want to stick to cvsup, you'll probably make it work again by portupgrade -fR 'cvsup*' 3. another approach is to get cvsup binaries from package instead of compiling ports - check man pkg_add 4. If you need cvsup to update ports tree, try portsnap instead. It's faster and smarter, and integrated with system :) - check man portsnap Good luck! //Niclas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Thanks for all the helpful suggestions. csup worked like a charm and solved the problem. I will be rebuilding my ports gradually, starting with the development ports like Perl, gcc, clang etc. I am also experimenting with a custom kernel where I am eliminating drivers and modules for isa, wireless devices and hardware only found on laptops. The early results are encouraging. I run fold...@home in a VirtualBox with Unbuntu x64 as a guest OS. Since trying a custom kernel, floating point performance has improved over 20%. This may also be due to some kernel improvements in FreeBSD 9. So far I am very impressed with the stability of the OS. I have not had problems with any of the programs that I run on a regular basis. I had expected to hit more bugs. I will get started on the rebuilds but with 1700 ports installed, I will wait for a free weekend to compile the big stuff. Thanks again Ralph Ellis ralphell...@netscape.ca ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[SPAM] Re: Error message while updating src for FreeBSD 9 current
On 2010-09-23 14:02, Bartosz Stec wrote: On 2010-09-23 13:36, Niclas Zeising wrote: On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the following error message when I do a src update. cvsup srcsupfile Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Edit src/bin/ps/extern.h Illegal instruction I am new to the mailing list. Is this a known error? Is this an error to do with the source tree or an issue on my end? Just for reference, the contents of my supfile are *default tag=. *default host=cvsup2.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress src-all ports-all doc-all Thanks in advance for your assistance, Ralph Ellis ralphell...@netscape.ca Are you using cvsup or csup? Have you recompiled cvsup in case you use that? What's in your make.conf file? Illegal instruction is usually because the program is compiled for another CPU than what it's running on. It can also be that syscalls has changed, but then it usually complains about that. When doing a major version upgrade, you usually have to recompile all ports. Hope this helps! //Niclas I am using cvsup. I had recompiled my VirtualBox port but I had not finished recompiling the other major ports. Thanks for the suggestion. My make.conf is deliberately very plain jane with no special conditions or comments. Thanks Ralph Ellis ralphell...@netscape.ca Try to recompile everything, or at least cvsup, and see if it works. //Niclas Niclas, did you perform 'make delete-old && make delete-old-libs' after upgrade to CURRENT? If you did, many of your ports won't longer work properly (or at all) because of missing libraries. If you didn't, you definitely should do something like 'portupgrade -afrRi' and after you done, you can get rid of these old files with commands above. You wouldn't get illegal instruction then though. Usually the application fails to load if dynamic libraries are missing. Of course it could take VERY long time depending on installed ports and machine spec., so if you just need to get your sources updated quickly I recommend: 1. Try csup instead of cvsup. It's integrated in both 8.x and in CURRENT, so should work "out of the box" That's a good idea. 2. If you (for some strange reasons) want to stick to cvsup, you'll probably make it work again by portupgrade -fR 'cvsup*' 3. another approach is to get cvsup binaries from package instead of compiling ports - check man pkg_add 4. If you need cvsup to update ports tree, try portsnap instead. It's faster and smarter, and integrated with system :) - check man portsnap Good luck! //Niclas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [SPAM] Re: Error message while updating src for FreeBSD 9 current
On 2010-09-23 13:36, Niclas Zeising wrote: On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the following error message when I do a src update. cvsup srcsupfile Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Edit src/bin/ps/extern.h Illegal instruction I am new to the mailing list. Is this a known error? Is this an error to do with the source tree or an issue on my end? Just for reference, the contents of my supfile are *default tag=. *default host=cvsup2.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress src-all ports-all doc-all Thanks in advance for your assistance, Ralph Ellis ralphell...@netscape.ca Are you using cvsup or csup? Have you recompiled cvsup in case you use that? What's in your make.conf file? Illegal instruction is usually because the program is compiled for another CPU than what it's running on. It can also be that syscalls has changed, but then it usually complains about that. When doing a major version upgrade, you usually have to recompile all ports. Hope this helps! //Niclas I am using cvsup. I had recompiled my VirtualBox port but I had not finished recompiling the other major ports. Thanks for the suggestion. My make.conf is deliberately very plain jane with no special conditions or comments. Thanks Ralph Ellis ralphell...@netscape.ca Try to recompile everything, or at least cvsup, and see if it works. //Niclas Niclas, did you perform 'make delete-old && make delete-old-libs' after upgrade to CURRENT? If you did, many of your ports won't longer work properly (or at all) because of missing libraries. If you didn't, you definitely should do something like 'portupgrade -afrRi' and after you done, you can get rid of these old files with commands above. Of course it could take VERY long time depending on installed ports and machine spec., so if you just need to get your sources updated quickly I recommend: 1. Try csup instead of cvsup. It's integrated in both 8.x and in CURRENT, so should work "out of the box" 2. If you (for some strange reasons) want to stick to cvsup, you'll probably make it work again by portupgrade -fR 'cvsup*' 3. another approach is to get cvsup binaries from package instead of compiling ports - check man pkg_add 4. If you need cvsup to update ports tree, try portsnap instead. It's faster and smarter, and integrated with system :) - check man portsnap Good luck! -- Bartosz Stec ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[SPAM] Re: Error message while updating src for FreeBSD 9 current
On 2010-09-23 13:21, Ralph Ellis wrote: Niclas Zeising wrote: On 2010-09-23 04:29, Ralph Ellis wrote: Hi, I recently upgraded my FreeBSD 8.1 installation to FreeBSD 9 current via buildworld and buildkernel. I was able to one general ports, src and doc update by cvsup but now I am getting the following error message when I do a src update. cvsup srcsupfile Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Edit src/bin/ps/extern.h Illegal instruction I am new to the mailing list. Is this a known error? Is this an error to do with the source tree or an issue on my end? Just for reference, the contents of my supfile are *default tag=. *default host=cvsup2.FreeBSD.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress src-all ports-all doc-all Thanks in advance for your assistance, Ralph Ellis ralphell...@netscape.ca Are you using cvsup or csup? Have you recompiled cvsup in case you use that? What's in your make.conf file? Illegal instruction is usually because the program is compiled for another CPU than what it's running on. It can also be that syscalls has changed, but then it usually complains about that. When doing a major version upgrade, you usually have to recompile all ports. Hope this helps! //Niclas I am using cvsup. I had recompiled my VirtualBox port but I had not finished recompiling the other major ports. Thanks for the suggestion. My make.conf is deliberately very plain jane with no special conditions or comments. Thanks Ralph Ellis ralphell...@netscape.ca Try to recompile everything, or at least cvsup, and see if it works. //Niclas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[SPAM] Re: Official request: Please make GNU grep the default
On 2010-08-20 11:10, Dag-Erling Smørgrav wrote: If you have profiling libraries installed, you can build a profiling version of grep (or any program) like so: % cd /usr/src/usr.bin/grep % make clean % make DEBUG_FLAGS="-pg -g" -DNO_SHARED Do *not" make install, because the result will be dog slow and you don't want to use it in production. Every time you run it, it will leave a file named grep.gmon in your current directory, so: As a side note, this maybe should be posted in the handbook and/or on the wiki for reference, so people who want to profile slow applications know how to do it. Regards! //Niclas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Regarding recent spam on the list
From: "Brandon S. Allbery KF8NH" <[EMAIL PROTECTED]> > On Tue, 2003-08-19 at 18:03, Bill Moran wrote: > > Just curious if anyone knows the origin of all these auto-responses, etc. > > > > I'm seeing a lot of these on every list I'm subscribed to (not all of them > > FreeBSD related) so I was wondering if some Windows trojan is running rampant > > and using these list addresses as return addys? > > It's W32/[EMAIL PROTECTED] It's spreading *fast* > The first day it appeared, I received 8000+ virus and virus warning messages in my inbox. The only way I could stop it from filling my inbox was to change my e-mail address, and place a permanent failure code in the access table for the old address. But, our mail server was still getting a Denial of Service, since it would max out the connections to both our primary and secondary mail servers. Today I believe I have solved the problem. I wrote a couple of scripts, that retrieves the IP address from the maillog for all servers/virus infected systems that are using the old email address. Then I setup IPFW to deny access to port 25 for these IP addresses. So far IPFW is dening access to our mail servers for 30,000 Class C's (/24). Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
