iftd@reaalsns.nl | 10 Nov 16:54 2014

con respecto a mi último correo electrónico

A la atención de :
Tengo algo de información vital para usted en relación con una
herencia que se quiso dar a usted.

E-mail o teléfono me llaman para que yo pueda darle una amplia
desglose en este proyecto .

David Boucher

freebsd-stable <at> freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Luciana | 10 Nov 12:11 2014



                                  Bom dia.

      Gostaria atender sua empresa em telefonia mvel, agora j podemos
                       tratar do plano dos celulares?

    Entraram vrios novos modelos de Smatphones, e os valores de internet
    diminuram, posso te fazer proposta da Claro baseada no uso atual de
                                sua empresa?

   Basta me passar mais ou menos com quantas linhas a empresa est hoje, e
              quantas precisam de internet, eu fao a proposta.

                          Agradeo antecipadamente.

                              Luciana Marcelino

                 Gerente de contas | Claro | Embratel | NET

                       Tel.: (11) 4318-0643 ramal: 113

                            Cel.: (11) 98815-8575

                   luciana.marcelino <at> claroembratel.com.br

   Segue minha nova carta de apresentao, agora com telefonia e internet
               fixa: [1]http://claroembratel.com.br/carta.pdf

              R. Marechal Deodoro, 458 - Santa Paula - SCS - SP
(Continue reading)

jungle Boogie | 9 Nov 04:04 2014

Svn West down?

Hello All,

I'm trying to update my ten stable machine but I receive a message that the
west location is unreachable.


Is anyone else experiencing the some issue? Is this a planned outage?

freebsd-stable <at> freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Darren Pilgrim | 9 Nov 00:59 2014

Request for r261231 backport to 10.0

10.0 i386 introduced a bug in cron that results in it running jobs at 
the wrong time[1].  r261231[2] MFC'd the fix to 10-stable, but after 
10.0-R.  10.1 is due in a few days, but it will be at least a month 
before move to 10.1 because I wait a bit for problems that tend to crop 
up only after release.

Building cron from stable/10 r261231 and copying it over /usr/sbin/cron 
on my 10.0 systems fixes the issue, but that's an evil hack.

Can we get this backported to 10.0 as an errata fix?

1: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194236
2: https://svnweb.freebsd.org/base?view=revision&revision=261231
freebsd-stable <at> freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

E-ZPass Info | 8 Nov 04:16 2014

Pay for driving on toll road






  Service Center









(Continue reading)

Eugene M. Zheganin | 7 Nov 16:47 2014

pxeboot and /boot/boot.4th


I'm using pxeboot to boot up an old box which is unable to boot from
it's own disks (for several uninteresting reasons). I'm booting it from
the TFTP. Everything is working as expected, except one thing: before
the kernel pxeboot tries to load up the /boot/boot.4th file and the
/boot/boot.4th.gz. While doing this, it ignores the messages from the
tftpd that there's no such file. If I create this (or these) file it
requests them both several times in cycle (requesting, but not trying to
read). After this everything boots up as usual.

How can I get rid off this boot.4th requests ?

freebsd-stable <at> freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Anton Shterenlikht | 6 Nov 14:47 2014

Re: ia64 10-stable buildworld failure: usr/src/usr.sbin/pw/pw_user.c:341: warning: signed and unsigned type in conditional expression

Asking on stable <at>  too.

>From mexas Thu Nov  6 13:46:08 2014
>To: freebsd-ia64 <at> freebsd.org
>Subject: ia64 10-stable buildworld failure: usr/src/usr.sbin/pw/pw_user.c:341: warning: signed
and unsigned type in conditional expression
>Reply-To: mexas <at> bris.ac.uk
>I'm updating a 10-stable poudriere jail on ia64 from
># poudriere jail -l
>ia64-10  10.1-PRERELEASE r273463 ia64 svn+https 2014-10-22 14:51:39 /pdr/jails/ia64-10
>to some today's.
>BTW, I can't seem to be able to find
>what revision it's building. Any hints?
>I get to:
>cc1: warnings being treated as errors
>/pdr/jails/ia64-10/usr/src/usr.sbin/pw/pw_user.c: In function 'pw_user':
>/pdr/jails/ia64-10/usr/src/usr.sbin/pw/pw_user.c:341: warning: signed and unsigned type in
conditional expression
>/pdr/jails/ia64-10/usr/src/usr.sbin/pw/pw_user.c:808: warning: signed and unsigned type in
conditional expression
>*** [pw_user.o] Error code 1
(Continue reading)

Kai Gallasch | 6 Nov 00:32 2014

10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout


Not sure if this is 10.1 related or more a problem of the ssd
model and/or ahci controller..

I am currently running 10.1 RC4 r273903 on a zfs on root server with two
mirror pools. One of the pools is a mirror consisting of two Samsung
SSD 850 PRO 512GB SSDs.

When I start a zfs scrub on this pool the result of the scrub is:

# zpool status -v ssdpool
  pool: ssdpool
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
	attempt was made to correct the error.  Applications are
unaffected. action: Determine if the device needs to be replaced, and
clear the errors using 'zpool clear' or replace the device with 'zpool
replace'. see: http://illumos.org/msg/ZFS-8000-9P
  scan: scrub repaired 73K in 0h8m with 0 errors on Thu Nov  6 00:00:16
2014 config:

	ssdpool           ONLINE       0     0     0
	  mirror-0        ONLINE       0     0     0
	    gpt/ssdpool0  ONLINE       0     0    17
	    gpt/ssdpool1  ONLINE       0     0    29

When I do a 'zpool clear' the pool status looks ok again. But when I
(Continue reading)

Pete French | 5 Nov 19:23 2014

Advice on an odd networking problem

I have some ouzzling behaviour here - looks very much like
I am running out of network resources of some kind, but I cant find
out what, so am wondering if anyone has any ideas.

All machines are running FreeBSD 9.2-STABLE r265427 - which is from
the start of May (probbaly around heartbleed time!)

We have 5 machines running webservers - apache24 serving cgi scripts,
plyus nginx being used to drive uwsgi with some django/python based
code. These are load balanced by pound on a machine which faces
the internet. This all works as expected, except that if I modify
the cgi-scripts running inside Apache so they make some https
calls to the nginx server on then what we see is that
pound then stops being able to connect to Apache for a proportion
of its calls - its returns 503's.

The effect on the calls which fail are as if the webserver is
not listening anymore. But this only applies to a fraction of
the calls - most get through. If I disable the cuntionality
which makes the intrenal call to then the problem
goes away.

It looks to me like I am runing out of some network resource somwhow,
but the load is very very low, and I cant see any obvious parameters
hitting their limits. Nothing is looged out of the ordinary on
the webservers, the only symptoom is the load balancer not being
able to connect.

Does anyone have any ideas where to look for a solution ? It is
puzzling the hell out of me!
(Continue reading)

Peter Ankerstål | 5 Nov 15:30 2014

freebsd-udapte upgrade.

Could someone please explain how to use freebsd-update upgrade without 
destroying all of your configuration files?

I really don’t understand how to use the merge function.. In this case i 
typed :q for all files it asked about. :wq seem to
do about the same thing. Notice that a few of the files has this shit in 
multiple places. I can’t be right that I should edit every file manually 
and look for “current version” and so on?

# grep "<< current" *
crontab:<<<<<<< current version
dhclient.conf:<<<<<<< current version
group:<<<<<<< current version
hosts:<<<<<<< current version
inetd.conf:<<<<<<< current version
master.passwd:<<<<<<< current version
motd:<<<<<<< current version
ntp.conf:<<<<<<< current version
passwd:<<<<<<< current version
services:<<<<<<< current version
shells:<<<<<<< current version
snmpd.config:<<<<<<< current version
syslog.conf:<<<<<<< current version
syslog.conf:<<<<<<< current version
ttys:<<<<<<< current version
ttys:<<<<<<< current version

# grep "<< current" */*
mail/freebsd.cf:<<<<<<< current version
mail/freebsd.cf:<<<<<<< current version
(Continue reading)

Matthew Seaman | 5 Nov 12:49 2014

Varnish proxy goes catatonic under heavy load

Dear all,

We had an unfortunate set of circumstances which resulted in several
million people all trying to download about 1.5MB worth of images from
our servers over the course of a few hours.  Or, at least, it would have
been a few hours, except that our three varnish proxies just crumbled
under the load within 10 minutes.

Now, that's bad enough, but we could have just about coped if the
proxies stopped serving requests for a few minutes.  What actually
happened was that all three servers went catatonic on the network *and
stayed that way*: even when we shunted the traffic away from one, we
still couldn't access it via ssh or any network protocol.  And it stayed
like that for sufficiently long time that we had no recourse other than
to get the servers rebooted.

Can anyone explain what was happening here?  Not having the servers
recover accessibility for an extended period even after the excess
traffic was stopped is unacceptable.  We're also struggling to recreate
the effect in the lab: any clues about how to do so, and any suggestions
about how to prevent the 'going catatonic' response would be greatly

Servers are amd64 running FreeBSD 9.1 or 9.2 and Varnish 3.0.5.



(Continue reading)