Date: Sat, 15 Oct 2011 14:34:41 +0200 From: kapral <kapral@toya.net.pl> To: <freebsd-stable@freebsd.org> Subject: Re: freebsd-stable Digest, Vol 430, Issue 6 Message-ID: <3299ac22cd607dc3e5d6763e66e67cd1@toya.net.pl> In-Reply-To: <20111015120030.3B5A910656E9@hub.freebsd.org> References: <20111015120030.3B5A910656E9@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
ok thx for explenation i just wonder why someone take control over my freebsd just after i turn on a browser under kde besides there should be no connections browser should be silent like lynx i think this is a bug On Sat, 15 Oct 2011 12:00:30 +0000 (UTC), freebsd-stable-request@freebsd.org wrote: > Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-request@freebsd.org > > You can reach the person managing the list at > freebsd-stable-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." > > > Today's Topics: > > 1. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Jilles Tjoelker) > 2. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Stefan Bethke) > 3. backup for /var/db/ports (Oleg Ginzburg) > 4. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Mikolaj Golub) > 5. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Mikolaj Golub) > 6. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Mikolaj Golub) > 7. Re: ports index on FreeBSD 9 (George Kontostanos) > 8. Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs (Stefan Bethke) > 9. unix browsers problem (kapral) > 10. Re: unix browsers problem (Stefan Bethke) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 14 Oct 2011 14:03:37 +0200 > From: Jilles Tjoelker <jilles@stack.nl> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Adrian Wontroba <aw1@stade.co.uk>, "freebsd-stable@freebsd.org" > <freebsd-stable@freebsd.org>, Mikolaj Golub <to.my.trociny@gmail.com> > Message-ID: <20111014120336.GB31718@stack.nl> > Content-Type: text/plain; charset=us-ascii > > On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: >> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: >> > I won't be in a position to create a simpler test case, raise a PR or >> > try patches till Tuesday evening (UK) at the earliest. > >> So far I have been unable to reproduce the problem with portupgrade (and >> will probably move to portmaster). > >> I have however found a different but possibly related problem with the >> new version of script in RELENG_8, for which I have raised this PR: > >> misc/161526: script outputs corrupt if input is not from a terminal > >> Blast, should of course been bin/ > > The extra ^D\b\b are the EOF character being echoed. These EOF > characters are being generated by the new script(1) to pass through the > EOF condition on stdin. > > One fix would be to change the termios settings temporarily to disable > the echoing but this may cause problems if the application is changing > termios settings concurrently and generally feels bad. > > It may be best to remove writing EOF characters, perhaps adding an > option to enable it again if there is a concrete use case for it. > > -- > Jilles Tjoelker > > > ------------------------------ > > Message: 2 > Date: Fri, 14 Oct 2011 22:50:32 +0200 > From: Stefan Bethke <stb@lassitu.de> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Jilles Tjoelker <jilles@stack.nl> > Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Mikolaj > Golub <to.my.trociny@gmail.com> > Message-ID: <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> > Content-Type: text/plain; charset=us-ascii > > > Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker: > >> On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: >>> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: >>>> I won't be in a position to create a simpler test case, raise a PR or >>>> try patches till Tuesday evening (UK) at the earliest. >> >>> So far I have been unable to reproduce the problem with portupgrade (and >>> will probably move to portmaster). >> >>> I have however found a different but possibly related problem with the >>> new version of script in RELENG_8, for which I have raised this PR: >> >>> misc/161526: script outputs corrupt if input is not from a terminal >> >>> Blast, should of course been bin/ >> >> The extra ^D\b\b are the EOF character being echoed. These EOF >> characters are being generated by the new script(1) to pass through the >> EOF condition on stdin. >> >> One fix would be to change the termios settings temporarily to disable >> the echoing but this may cause problems if the application is changing >> termios settings concurrently and generally feels bad. >> >> It may be best to remove writing EOF characters, perhaps adding an >> option to enable it again if there is a concrete use case for it. > > I finally figured out why my ports aren't updating anymore: when running > portupgrade -a --batch from cron, stdin is /dev/null, and that produces the > gobs of ^D in the output, as well as the script file that portupgrade > creates. What's worse is that the upgrade never completes. > > You can easily see this for yourself: > # portupgrade -a --batch </dev/null > > This is on 8-stable from October 5th. > > > Stefan > > -- > Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 > > > > > > ------------------------------ > > Message: 3 > Date: Sat, 15 Oct 2011 04:48:19 +0400 > From: Oleg Ginzburg <olevole@olevole.ru> > Subject: backup for /var/db/ports > To: freebsd-stable@freebsd.org > Message-ID: <201110150448.19507.olevole@olevole.ru> > Content-Type: Text/Plain; charset="utf-8" > > Hi > > With /etc/periodic/daily/220.backup-pkgdb I would also suggest backing up > /var/db/ports dir > > Maybe it's better to combine into one script. > > diff -ruN etc.bak/defaults/periodic.conf etc/defaults/periodic.conf > --- etc.bak/defaults/periodic.conf 2011-10-15 04:37:28.879673119 +0400 > +++ etc/defaults/periodic.conf 2011-10-15 04:30:48.599677268 +0400 > @@ -78,6 +78,10 @@ > daily_backup_pkgdb_enable="YES" # Backup > /var/db/pkg > daily_backup_pkgdb_dir="/var/backups" > > +# 230.backup-portdb > +daily_backup_portdb_enable="YES" # Backup > /var/db/ports > +daily_backup_portdb_dir="/var/backups" > + > # 300.calendar > daily_calendar_enable="NO" # Run calendar -a > > diff -ruN etc.bak/periodic/daily/230.backup-portdb > etc/periodic/daily/230.backup-portdb > --- etc.bak/periodic/daily/230.backup-portdb 1970-01-01 > 03:00:00.000000000 > +0300 > +++ etc/periodic/daily/230.backup-portdb 2011-10-15 > 04:29:31.149682366 > +0400 > @@ -0,0 +1,51 @@ > +#!/bin/sh > +# > +# $FreeBSD: src/etc/periodic/daily/220.backup-portdb,v 1.2 2011/05/05 > 02:35:11 dougb Exp $ > +# > + > +# If there is a global system configuration file, suck it in. > +# > +if [ -r /etc/defaults/periodic.conf ] > +then > + . /etc/defaults/periodic.conf > + source_periodic_confs > +fi > + > +rc=0 > + > +case "$daily_backup_portdb_enable" in > + [Yy][Ee][Ss]) > + bak="${daily_backup_portdb_dir:-/var/backups}" > + bak_file="${bak}/portdb.bak.tbz" > + > + port_dbdir=`make -f/usr/share/mk/bsd.port.mk -V PORT_DBDIR > 2>/dev/null` || > + port_dbdir=/var/db/ports > + > + if [ ! -d "$bak" ] > + then > + install -d -o root -g wheel -m 750 $bak || { > + echo '$daily_backup_portdb_enable is enabled but' \ > + "$daily_backup_portdb_dbdir doesn't exist" ; > + exit 2 ; } > + fi > + > + echo '' > + echo 'Backing up package db directory:' > + > + new_bak_file=`mktemp ${bak_file}-XXXXX` > + > + if tar -cjHf "${new_bak_file}" "$port_dbdir" 2>/dev/null; then > + chmod 644 "${new_bak_file}" > + > + if [ -e "${bak_file}.2" -a -e "${bak_file}" ]; then > + unlink "${bak_file}.2" > + mv "${bak_file}" "${bak_file}.2" > + fi > + [ -e "${bak_file}" ] && mv "${bak_file}" "${bak_file}.2" > + mv "${new_bak_file}" "${bak_file}" > + else > + rc=3 > + fi ;; > +esac > + > +exit $rc > > > -- > С Ñважением, With respect, > Ðлег ÐинзбÑÑг Oleg Ginzburg > ================================= > E-mail: mailto: olevole@olevole.ru > Skype: olegginzburg > XMPP/Jabber: olevole@jabber.ru > > > > ------------------------------ > > Message: 4 > Date: Sat, 15 Oct 2011 10:25:16 +0300 > From: Mikolaj Golub <trociny@freebsd.org> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Adrian Wontroba <aw1@stade.co.uk> > Cc: Kostik Belousov <kib@FreeBSD.org>, "freebsd-stable@freebsd.org" > <freebsd-stable@freebsd.org>, Jilles Tjoelker <jilles@stack.nl> > Message-ID: <86zkh2k97n.fsf@kopusha.home.net> > Content-Type: text/plain; charset="us-ascii" > > > On Wed, 12 Oct 2011 23:25:35 +0100 Adrian Wontroba wrote: > > AW> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: > >> I won't be in a position to create a simpler test case, raise a PR or > >> try patches till Tuesday evening (UK) at the earliest. > > AW> So far I have been unable to reproduce the problem with portupgrade > (and > AW> will probably move to portmaster). > > AW> I have however found a different but possibly related problem with the > AW> new version of script in RELENG_8, for which I have raised this PR: > > AW> misc/161526: script outputs corrupt if input is not from a terminal > > As Jilles wrote ^D\b\b are echoed by the terminal when the script sends > VEOF > to the program being script. > > In my recent commit r225809 the intention was to sent VEOF only once if > STDIN > was not terminal. Unfortunately the fix was incorrect and for flushtime > 0 > it > keeps sending VEOF. That is why you are observing series of ^D\b\b > characters. > > I am going to commit the attached patch to HEAD, that fixes this. But we > will > still have one ^D\b\b in the output. > > -- > Mikolaj Golub > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: script.c.4.patch > Type: text/x-patch > Size: 690 bytes > Desc: not available > Url : > http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20111015/db3c0cad/script.c.4-0001.bin > > ------------------------------ > > Message: 5 > Date: Sat, 15 Oct 2011 10:31:06 +0300 > From: Mikolaj Golub <trociny@freebsd.org> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Jilles Tjoelker <jilles@stack.nl> > Cc: Kostik Belousov <kib@FreeBSD.org>, "freebsd-stable@freebsd.org" > <freebsd-stable@freebsd.org> > Message-ID: <86vcrqk8xx.fsf@kopusha.home.net> > Content-Type: text/plain; charset=us-ascii > > > On Fri, 14 Oct 2011 14:03:37 +0200 Jilles Tjoelker wrote: > > JT> On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: > >> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: > >> > I won't be in a position to create a simpler test case, raise a PR or > >> > try patches till Tuesday evening (UK) at the earliest. > > >> So far I have been unable to reproduce the problem with portupgrade > >> (and > >> will probably move to portmaster). > > >> I have however found a different but possibly related problem with the > >> new version of script in RELENG_8, for which I have raised this PR: > > >> misc/161526: script outputs corrupt if input is not from a terminal > > >> Blast, should of course been bin/ > > JT> The extra ^D\b\b are the EOF character being echoed. These EOF > JT> characters are being generated by the new script(1) to pass through > the > JT> EOF condition on stdin. > > JT> One fix would be to change the termios settings temporarily to disable > JT> the echoing but this may cause problems if the application is changing > JT> termios settings concurrently and generally feels bad. > > JT> It may be best to remove writing EOF characters, perhaps adding an > JT> option to enable it again if there is a concrete use case for it. > > Without passing EOF to the to the program being scripted the following > command > will hang forever: > > echo 1 |script /tmp/script.out cat > > -- > Mikolaj Golub > > > ------------------------------ > > Message: 6 > Date: Sat, 15 Oct 2011 10:36:04 +0300 > From: Mikolaj Golub <trociny@freebsd.org> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Stefan Bethke <stb@lassitu.de> > Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Jilles > Tjoelker <jilles@stack.nl> > Message-ID: <86r52ek8pn.fsf@kopusha.home.net> > Content-Type: text/plain; charset=us-ascii > > > On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote: > > SB> I finally figured out why my ports aren't updating anymore: when > running portupgrade -a --batch from cron, stdin is /dev/null, and that > produces the gobs of ^D in the output, as well as the script file that > portupgrade creates. What's worse is that the upgrade never completes. > > SB> You can easily see this for yourself: > SB> # portupgrade -a --batch </dev/null > > SB> This is on 8-stable from October 5th. > > Could you please try the patch I attached to another my mail in this thread > to > see if it helps? > > -- > Mikolaj Golub > > > ------------------------------ > > Message: 7 > Date: Sat, 15 Oct 2011 12:24:32 +0300 > From: George Kontostanos <gkontos.mail@gmail.com> > Subject: Re: ports index on FreeBSD 9 > To: Matthew Seaman <m.seaman@infracaninophile.co.uk> > Cc: "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, FreeBSD Stable > <freebsd-stable@freebsd.org> > Message-ID: > <CA+dUSyqkaNpvctAqaU3pcvMQinmjj1m-1am2gPNwt+S+P-tQ0Q@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Thu, Oct 13, 2011 at 2:54 AM, George Kontostanos > <gkontos.mail@gmail.com> wrote: >> On Wed, Oct 12, 2011 at 3:01 PM, Matthew Seaman >> <m.seaman@infracaninophile.co.uk> wrote: >>> On 12/10/2011 11:24, Sergey V. Dyatko wrote: >>>> On Wed, 12 Oct 2011 13:12:55 +0300 >>>> George Kontostanos <gkontos.mail@gmail.com> wrote: >>>> >>>>> On Wed, Oct 12, 2011 at 8:52 AM, Sergey V. Dyatko >>>>> <sergey.dyatko@gmail.com> wrote: >>>>>> On Tue, 11 Oct 2011 14:31:12 +0300 >>>>>> George Kontostanos <gkontos.mail@gmail.com> wrote: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> I was wondering if there is any progress regarding the >>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=149232 . >>>>>>> >>>>>>> >>>>>> >>>>>> svn log -v -r226274 >>>>> >>>>>> wbr, tiger >>>>>> >>>>> Do you mean this: >>>>> http://svnweb.freebsd.org/base?view=revision&revision=226274 ? >>>>> >>>>> >>>> >>>> oops, sorry, wrong revision. >>>> >>>> svn log -v -r226277 http://svn.freebsd.org/base/head >>>> >>>> >>> >>> MFC to stable/9 might be a good idea... >>> >>> Cheers, >>> >>> Matthew >>> >>> -- >>> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard >>> Flat 3 >>> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate >>> JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >>> >>> >> svn commit: r226322 - stable/9/etc >> >> Thanks everyone >> >> -- >> George Kontostanos >> aisecure.net >> > It still doesn't upgrade the index file properly : > > hp# portsnap fetch update && portversion -v | grep "<" > Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. > Fetching snapshot tag from portsnap5.FreeBSD.org... done. > Fetching snapshot metadata... done. > Updating from Thu Oct 6 11:21:13 EEST 2011 to Sat Oct 15 12:06:45 EEST > 2011. > Fetching 3 metadata patches.. done. > Applying metadata patches... done. > .... > .... > Building new INDEX files... done. > ezm3-1.1_2 < needs updating (port has 1.2_1) > > > hp# cd /usr/ports/ > hp# make fetchindex > /usr/ports/INDEX-9.bz2 100% of 1512 kB 183 kBps > hp# portversion -v | grep "<" > [Updating the portsdb <format:dbm_hash> in /usr/ports ... - 22730 port > entries found > .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000.........17000.........18000.........19000.........20000.........21000.........22000....... > ..... done] > ezm3-1.1_2 < needs updating (port has 1.2_1) > ffmpeg-0.7.5,1 < needs updating (port has 0.7.6,1) > libltdl-2.4 < needs updating (port has 2.4_1) > libtool-2.4 < needs updating (port has 2.4_1) > mpfr-3.0.1 < needs updating (port has 3.1.0_1) > p5-Authen-NTLM-1.08_1 < needs updating (port has 1.09) > p5-Class-Load-0.10 < needs updating (port has 0.11) > p5-DateTime-TimeZone-1.36 < needs updating (port has 1.39) > p5-Module-Metadata-1.000006 < needs updating (port has 1.000007) > phpMyAdmin-3.4.5 < needs updating (port has 3.4.6.r1) > x264-0.115.2000 < needs updating (port has 0.116.2076) > > > > -- > George Kontostanos > aisecure.net > > > ------------------------------ > > Message: 8 > Date: Sat, 15 Oct 2011 11:50:22 +0200 > From: Stefan Bethke <stb@lassitu.de> > Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and > xargs > To: Mikolaj Golub <trociny@FreeBSD.org> > Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Jilles > Tjoelker <jilles@stack.nl> > Message-ID: <CF944885-8030-4585-B1D8-313C4CCEEB6B@lassitu.de> > Content-Type: text/plain; charset=us-ascii > > Am 15.10.2011 um 09:36 schrieb Mikolaj Golub: > >> >> On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote: >> >> SB> I finally figured out why my ports aren't updating anymore: when >> running portupgrade -a --batch from cron, stdin is /dev/null, and that >> produces the gobs of ^D in the output, as well as the script file that >> portupgrade creates. What's worse is that the upgrade never completes. >> >> SB> You can easily see this for yourself: >> SB> # portupgrade -a --batch </dev/null >> >> SB> This is on 8-stable from October 5th. >> >> Could you please try the patch I attached to another my mail in this >> thread to >> see if it helps? > > > Seems to do the trick, thanks! > > > Stefan > > -- > Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 > > > > > > ------------------------------ > > Message: 9 > Date: Sat, 15 Oct 2011 12:34:14 +0200 > From: kapral <kapral@toya.net.pl> > Subject: unix browsers problem > To: <freebsd-stable@freebsd.org> > Message-ID: <1b39c8399c008e3ee437586e0a408865@toya.net.pl> > Content-Type: text/plain; charset="UTF-8" > > When I connect with any freebsd 8.2 browsers like epithany konqueror > firefox7.0.1 and under open bsd 4.9 with firefox 3.6.13 en i have strange > connections too le100.net i checkt the ip and this is seedo in germany i > also have other strange connections any idea what to do with this bug ? > > > ------------------------------ > > Message: 10 > Date: Sat, 15 Oct 2011 13:49:59 +0200 > From: Stefan Bethke <stb@lassitu.de> > Subject: Re: unix browsers problem > To: kapral <kapral@toya.net.pl> > Cc: freebsd-stable@freebsd.org > Message-ID: <D860B6CF-A122-464A-8B24-379B037472F4@lassitu.de> > Content-Type: text/plain; charset=us-ascii > > Am 15.10.2011 um 12:34 schrieb kapral: > >> When I connect with any freebsd 8.2 browsers like epithany konqueror >> firefox7.0.1 and under open bsd 4.9 with firefox 3.6.13 en i have >> strange >> connections too le100.net i checkt the ip and this is seedo in germany i >> also have other strange connections any idea what to do with this bug ? > > I think you need to be much more specific about what you're seeing, and why > you think that it is a problem. > > I got curious, so I fired up a fresh Firefox, and indeed saw that I have > open connections to a couple of IPs: > $ netstat -anfinet > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 0 92.231.160.45.14944 74.125.43.120.80 > ESTABLISHED > tcp4 0 0 92.231.160.45.62441 74.125.43.104.80 > ESTABLISHED > tcp4 0 0 92.231.160.45.41710 74.125.43.104.80 > ESTABLISHED > tcp4 0 0 92.231.160.45.56705 195.95.193.85.80 > ESTABLISHED > tcp4 0 0 92.231.160.45.14474 195.95.193.78.80 TIME_WAIT > tcp4 0 0 92.231.160.45.64333 195.95.193.78.80 > ESTABLISHED > tcp4 0 0 92.231.160.45.36191 68.232.35.119.80 TIME_WAIT > tcp4 0 0 92.231.160.45.40339 63.245.217.43.443 TIME_WAIT > tcp4 0 0 92.231.160.45.51785 63.245.217.43.443 > ESTABLISHED > tcp4 0 0 92.231.160.45.51321 74.125.43.190.443 > ESTABLISHED > > The 74.125.43.* addresses do resolve to 1e100.net, as you're seeing: > $ host 74.125.43.190 > 190.43.125.74.in-addr.arpa domain name pointer bw-in-f190.1e100.net. > $ host 74.125.43.104 > 104.43.125.74.in-addr.arpa domain name pointer bw-in-f104.1e100.net. > > whois shows who's using them: > $ whois 74.125.43.104 > ... > NetRange: 74.125.0.0 - 74.125.255.255 > CIDR: 74.125.0.0/16 > OriginAS: > NetName: GOOGLE > NetHandle: NET-74-125-0-0-1 > Parent: NET-74-0-0-0-0 > NetType: Direct Allocation > RegDate: 2007-03-13 > Updated: 2007-05-22 > Ref: http://whois.arin.net/rest/net/NET-74-125-0-0-1 > > Considering that Firefox by default will open up the Firefox Google page, I > don't find this surprising at all. > > > Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3299ac22cd607dc3e5d6763e66e67cd1>