Re: recommended memory for zfs
On Fri, 10 May 2013 04:18:42 +0200, Benjamin Adams
wrote:
On 05/09/2013 10:06 PM, Jeremy Chadwick wrote:
On Thu, May 09, 2013 at 09:47:27PM -0400, Benjamin Adams wrote:
On 05/09/2013 08:53 PM, Shane Ambler wrote:
On 09/05/2013 22:48, Benjamin Adams wrote:
Hello zfs question about memory.
I heard zfs is very ram hungry.
Service looking to run:
- nginx
- postgres
- php-fpm
- python
I have a machine with two quad core cpus but only 4 G Memory
I'm looking to buy more ram now.
What would be the recommend amount of memory for zfs across 6 drives
on
this setup?
I believe I heard a calculation of 1GB cache per 1TB of disk. But
basically zfs will use all free ram available if you access that
much data from disk. You will want to set vfs.zfs.arc_max to allow
enough ram for your apps to work in.
If you consider the files for your website and the data you store
you may find that you would never fill more than 500MB of cache.
If you will be serving large media files that will easily use up
the cache you could give them their own filesystem that only
caches metadata - zfs set primarycache=metadata zroot/mediafiles
Thanks for all the replies Size of DB and HD's are:
Current DB Size = 23 GB
HD sizes = (6) 500 GB drives
Nobody is going to be able to give you a precise/accurate recommendation
given the lack of detail provided, I'm sorry to say. What's the RES
size of nginx (all processes combined)? What's the RES size of
postgres (same)? Do you have PHP scripts that "run amok" for long
periods of time and take up lots of RAM? Same with python? How many
concurrent visitors and what sort of content are you hosting? Do you
maintain/write your own PHP/Python code or are you using some crap like
Wordpress?
This is just a **small** list of questions -- and what may come as a
shock is that I do not expect you to provide answers to any of them.
They are questions that you should, for yourself, attempt to answer and
work out what you need from there ("teach a man to fish" and all that).
The advice of "1GB of RAM per 1TB of disk space" is absolute nonsense on
numerous levels -- whoever gave this advice to Shane either has no
understanding of how filesystems/ZFS works, or does but chose to
simplify to the point where they're providing half-ass information.
There is no direct, or even indirect, correlation between disk capacity
and ZFS ARC size -- what matter is your "working set" (to quote Tom).
You need to have some idea of how much disk I/O you're doing, and what
type of I/O (sequential or random).
If you want my general advice, Benjamin, it's this: get yourself a
system with *minimum* 8GB of RAM but has the physical possibility of
supporting more (and only add more RAM when/if you know you need it); do
not bother with ZFS on a system with 4GB. Run amd64, not i386 (I don't
recommend bothering with ZFS on i386 -- I am not going to get into a
discussion about this either). Run stable/9, not 9.1-RELEASE. Avoid
compression and dedup. And test disk failures as well (don't get caught
with your pants down later).
The above advice comes from someone who did hosting (web/ssh/etc.) for
almost 20 years with KISS principle applied at all levels. YMMV though,
depending on what all you're doing/what you truly need.
Good luck.
Jeremy,
Was just see if I should just get raid controller and more ram down the
road.
List of priorities.
Main thing is I move from BSD when 9.0 came out. Was looking to see if
zfs is included in the installer. Now.
Sum up:
upgrade ram to 16GB (not 64 like plained)
and raid controller that supports level 5.
Let ZFS do the RAID stuff. Do not use a RAID controller, but give the
plain disks to ZFS. Some of the nice features come from ZFS doing the RAID
stuff.
Ronald.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: recommended memory for zfs
On May 10, 2013, at 1:08 PM, "Ronald Klop" wrote:
> On Fri, 10 May 2013 04:18:42 +0200, Benjamin Adams
> wrote:
>
>> On 05/09/2013 10:06 PM, Jeremy Chadwick wrote:
>>> On Thu, May 09, 2013 at 09:47:27PM -0400, Benjamin Adams wrote:
On 05/09/2013 08:53 PM, Shane Ambler wrote:
> On 09/05/2013 22:48, Benjamin Adams wrote:
>> Hello zfs question about memory.
>> I heard zfs is very ram hungry.
>> Service looking to run:
>> - nginx
>> - postgres
>> - php-fpm
>> - python
>>
>> I have a machine with two quad core cpus but only 4 G Memory
>>
>> I'm looking to buy more ram now.
>> What would be the recommend amount of memory for zfs across 6 drives on
>> this setup?
>>
> I believe I heard a calculation of 1GB cache per 1TB of disk. But
> basically zfs will use all free ram available if you access that
> much data from disk. You will want to set vfs.zfs.arc_max to allow
> enough ram for your apps to work in.
>
> If you consider the files for your website and the data you store
> you may find that you would never fill more than 500MB of cache.
>
> If you will be serving large media files that will easily use up
> the cache you could give them their own filesystem that only
> caches metadata - zfs set primarycache=metadata zroot/mediafiles
>
>
Thanks for all the replies Size of DB and HD's are:
Current DB Size = 23 GB
HD sizes = (6) 500 GB drives
>>> Nobody is going to be able to give you a precise/accurate recommendation
>>> given the lack of detail provided, I'm sorry to say. What's the RES
>>> size of nginx (all processes combined)? What's the RES size of
>>> postgres (same)? Do you have PHP scripts that "run amok" for long
>>> periods of time and take up lots of RAM? Same with python? How many
>>> concurrent visitors and what sort of content are you hosting? Do you
>>> maintain/write your own PHP/Python code or are you using some crap like
>>> Wordpress?
>>>
>>> This is just a **small** list of questions -- and what may come as a
>>> shock is that I do not expect you to provide answers to any of them.
>>> They are questions that you should, for yourself, attempt to answer and
>>> work out what you need from there ("teach a man to fish" and all that).
>>>
>>> The advice of "1GB of RAM per 1TB of disk space" is absolute nonsense on
>>> numerous levels -- whoever gave this advice to Shane either has no
>>> understanding of how filesystems/ZFS works, or does but chose to
>>> simplify to the point where they're providing half-ass information.
>>> There is no direct, or even indirect, correlation between disk capacity
>>> and ZFS ARC size -- what matter is your "working set" (to quote Tom).
>>> You need to have some idea of how much disk I/O you're doing, and what
>>> type of I/O (sequential or random).
>>>
>>> If you want my general advice, Benjamin, it's this: get yourself a
>>> system with *minimum* 8GB of RAM but has the physical possibility of
>>> supporting more (and only add more RAM when/if you know you need it); do
>>> not bother with ZFS on a system with 4GB. Run amd64, not i386 (I don't
>>> recommend bothering with ZFS on i386 -- I am not going to get into a
>>> discussion about this either). Run stable/9, not 9.1-RELEASE. Avoid
>>> compression and dedup. And test disk failures as well (don't get caught
>>> with your pants down later).
>>>
>>> The above advice comes from someone who did hosting (web/ssh/etc.) for
>>> almost 20 years with KISS principle applied at all levels. YMMV though,
>>> depending on what all you're doing/what you truly need.
>>>
>>> Good luck.
>>>
>> Jeremy,
>>
>> Was just see if I should just get raid controller and more ram down the road.
>> List of priorities.
>>
>> Main thing is I move from BSD when 9.0 came out. Was looking to see if zfs
>> is included in the installer. Now.
>>
>> Sum up:
>> upgrade ram to 16GB (not 64 like plained)
>> and raid controller that supports level 5.
>>
>
> Let ZFS do the RAID stuff. Do not use a RAID controller, but give the plain
> disks to ZFS. Some of the nice features come from ZFS doing the RAID stuff.
To paraphrase this.
Get yourself a nice HBA. non-RAID! For example, something based on LSI2008 with
IT firmware. With few enough discs you can avoid using SAS expanders as well.
RAID controllers, in addition to causing all kinds of troubles are unlikely to
have sufficient bandwidth and might turn out to be the bottleneck (unless you
are prepared to spend an unholy amount of money -- which are better spent for
RAM and CPU).
If you want performance and low latency, avoid using compression and dedup in
ZFS. Set your record size appropriately for postgresql (8k) *before* you run
initdb. It is best to create an separate filesystem for the database and set
that property only there. If your database is heavy on updates, you might be
interested to use an SSD for ZIL. In ge
Re: new jail(8) ignoring devfs_ruleset?
On 05/09/13 22:42, Dewayne Geraghty wrote: An ugly workaround to complete the jail closure, when relying on jail.conf, is to: jail -r $JAILNAME umount /$LOCATION_OF_JAILS/$JAILNAME/dev || true The only problem with devfs I'm aware of is it not catching the right ruleset when starting in the rc system. So does this mean you're having problems unmounting /dev? What happens when you add a "-v" to the "jail -r"? It should note that /dev is being umounted. - Jamie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Generating ISO With Pre-Installed Packages
Hey All, I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that has certain packages pre-installed. I'd like to create my own installation media that will have certain things installed, like a web management UI that I'm actively working on. It'd be like what pfSense does. I did do a little googling and found pfSense's build documentation for spinning a custom build of pfSense. I'll be spending the weekend looking over their work. But in the meantime, does anyone know of the steps involved in such a process? Is the process documented somewhere? Thanks, Shawn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Generating ISO With Pre-Installed Packages
On Fri, May 10, 2013 at 9:55 AM, Shawn Webb wrote: > Hey All, > > I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that > has certain packages pre-installed. I'd like to create my own installation > media that will have certain things installed, like a web management UI > that I'm actively working on. It'd be like what pfSense does. > > I did do a little googling and found pfSense's build documentation for > spinning a custom build of pfSense. I'll be spending the weekend looking > over their work. But in the meantime, does anyone know of the steps > involved in such a process? Is the process documented somewhere? You're looking for package-split.py, a python script that generates packages. The blog post below may be of some use. It explains modifying the script and generating a release. http://blog.hostileadmin.com/2012/10/08/building-freebsd-media-with-custom-packages/ -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Generating ISO With Pre-Installed Packages
As Rick pointed out, the package split script will get the packages on the media. You also need to modify the install process to actually install the default packages. You might want to look at the bsdinstall setup and add a script there to load the packages. Another approach is to create a script that runs on first boot that can install the packages via network or possibly off the media. For MidnightBSD, I created a firstboot script that prompts the user to install a graphical desktop environment and the fetched meta packages from our ports tree that would pull down everything required for kde or GNUstep + window maker. It was easier as we had sysinstall still. Lucas Holt On May 10, 2013, at 9:55 AM, Shawn Webb wrote: > Hey All, > > I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that > has certain packages pre-installed. I'd like to create my own installation > media that will have certain things installed, like a web management UI > that I'm actively working on. It'd be like what pfSense does. > > I did do a little googling and found pfSense's build documentation for > spinning a custom build of pfSense. I'll be spending the weekend looking > over their work. But in the meantime, does anyone know of the steps > involved in such a process? Is the process documented somewhere? > > Thanks, > > Shawn > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Apparent regression in r250359
This patch works on one of my 9.1 systems in addition to my CURRENT
system.
On Thu, 9 May 2013, Jim Ohlstein wrote:
On 05/09/13 12:04, Konstantin Belousov wrote:
On Thu, May 09, 2013 at 11:42:28AM -0400, Jim Ohlstein wrote:
On 05/09/13 10:30, Konstantin Belousov wrote:
On Thu, May 09, 2013 at 10:13:15AM -0400, Jim Ohlstein wrote:
# sysctl hw.model
hw.model: AMD FX(tm)-8350 Eight-Core Processor
Ahh, so it seems that this is a CPU with the LWP.
Please try the patch at the end of message.
Same error
As another workaround, which does not disable AVX support, you
could try loader tunable hw.xsave_mask=0x7.
This works
Hm, I see another bug in the next line as well. Could you try this
updated patch ?
This does work.
diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c
index de79baa..9bc8a2f 100644
--- a/sys/amd64/amd64/fpu.c
+++ b/sys/amd64/amd64/fpu.c
@@ -687,8 +687,8 @@ fpugetregs(struct thread *td)
offsetof(struct xstate_hdr, xstate_bv));
max_ext_n = flsl(xsave_mask);
for (i = 0; i < max_ext_n; i++) {
- bit = 1 << i;
- if ((*xstate_bv & bit) != 0)
+ bit = 1ULL << i;
+ if ((xsave_mask & bit) == 0 || (*xstate_bv & bit) !=
0)
continue;
bcopy((char *)fpu_initialstate +
xsave_area_desc[i].offset,
--
Jim Ohlstein
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 It has been suggested to me (by a committer) that I should raise the issue of this PR here on these lists, because the problem described within the PR remains a real problem, and despite my having proposed something that seems to be a perfectly workable fix, no action has been taken on this PR for some years now. Regards, rfg P.S. The following additional PRs, also filed by me and also relating to the script(1) command, supply some additional improvements to efficiency and code clarity. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152131 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152132 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
Hi! > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 > > It has been suggested to me (by a committer) that I should raise the > issue of this PR here on these lists, because the problem described > within the PR remains a real problem, and despite my having proposed > something that seems to be a perfectly workable fix, no action has > been taken on this PR for some years now. Having looked at the PR, may I suggest that you look at sysutils/screen and screen -L especially instead of script -k -- and add some input logging to screen ? Or, for the tmux fraction, at sysutils/tmux ? I'm not sure why you absolutly *need* the input logging -- can you describe the use case ? Is it some security-audit-issue ? -- p...@opsec.eu+49 171 3101372 7 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh)
In message <20130510213610.gg8...@home.opsec.eu>, you wrote: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154 >> >> It has been suggested to me (by a committer) that I should raise the >> issue of this PR here on these lists, because the problem described >> within the PR remains a real problem, and despite my having proposed >> something that seems to be a perfectly workable fix, no action has >> been taken on this PR for some years now. > >Having looked at the PR, may I suggest that you look at sysutils/screen >and screen -L especially instead of script -k -- and add some >input logging to screen ? Or, for the tmux fraction, at sysutils/tmux ? Where I come from, we have a very common saying "It's a free country!" Thus, you may indeed make that suggestion. In fact you are free to suggest anything you like. Unfortunately, I currently already have an overflowing TO-DO list and I am not taking anything more onto my own personal plate at this time. >I'm not sure why you absolutly *need* the input logging -- can you >describe the use case ? Is it some security-audit-issue ? I really do not intend to be at all rude, but... I'm not sure why you are asking _me_ to defend the existance of the script -k option. I probably could do so, but that is rather besides the point, I think. The option exists, and has existed, for quite a long time. At some time in the ancient past, presumably when dinosaurs (and perhaps even Richie, Thompson, & Kernighan) roamed the earth, someone somewhere thought that being able to have script(1) log both input and output was a Good Idea[tm] and the -k option was born. Unfortunately, in FreeBSD, that option is buggy. It doesn't work right. It doesn't work according to specification. I proposed a way (code) to fix that. That's all. If you want to debate the merits of the very existance of the script program, or any option thereof, I'll be more than happy to do so anytime over a beer... as long as you are buying. In the meantime may I suggest that the easily verifiable bug that I originally filed a PR on should be fixed? Regards, rfg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on mips/mips
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for mips/mips TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=mips TB --- 2013-05-10 23:05:16 - TARGET_ARCH=mips TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -EL -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:38:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:38:22 - ERROR: failed to build world TB --- 2013-05-10 23:38:22 - 1619.40 user 348.73 system 1990.52 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-mips-mips.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on arm/arm
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for arm/arm TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=arm TB --- 2013-05-10 23:05:16 - TARGET_ARCH=arm TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:38:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:38:52 - ERROR: failed to build world TB --- 2013-05-10 23:38:52 - 1672.59 user 375.45 system 2020.77 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-arm-arm.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on i386/pc98
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=pc98 TB --- 2013-05-10 23:05:16 - TARGET_ARCH=i386 TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:47:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:47:25 - ERROR: failed to build world TB --- 2013-05-10 23:47:25 - 2121.22 user 388.45 system 2533.12 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on i386/i386
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=i386 TB --- 2013-05-10 23:05:16 - TARGET_ARCH=i386 TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:47:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:47:57 - ERROR: failed to build world TB --- 2013-05-10 23:47:57 - 2147.98 user 386.24 system 2565.10 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on amd64/amd64
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=amd64 TB --- 2013-05-10 23:05:16 - TARGET_ARCH=amd64 TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:48:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:48:22 - ERROR: failed to build world TB --- 2013-05-10 23:48:22 - 2162.48 user 393.04 system 2590.05 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-amd64-amd64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on ia64/ia64
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2013-05-10 23:05:12 - cleaning the object tree TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:05:15 - At svn revision 250487 TB --- 2013-05-10 23:05:16 - building world TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null TB --- 2013-05-10 23:05:16 - TARGET=ia64 TB --- 2013-05-10 23:05:16 - TARGET_ARCH=ia64 TB --- 2013-05-10 23:05:16 - TZ=UTC TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:05:16 - cd /src TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:05:17 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-10 23:59:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-10 23:59:59 - ERROR: failed to build world TB --- 2013-05-10 23:59:59 - 2852.12 user 412.70 system 3287.60 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on sparc64/sparc64
TB --- 2013-05-10 23:38:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:38:53 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:38:53 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2013-05-10 23:38:53 - cleaning the object tree TB --- 2013-05-10 23:38:53 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:38:55 - At svn revision 250487 TB --- 2013-05-10 23:38:56 - building world TB --- 2013-05-10 23:38:56 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:38:56 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:38:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:38:56 - SRCCONF=/dev/null TB --- 2013-05-10 23:38:56 - TARGET=sparc64 TB --- 2013-05-10 23:38:56 - TARGET_ARCH=sparc64 TB --- 2013-05-10 23:38:56 - TZ=UTC TB --- 2013-05-10 23:38:56 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:38:56 - cd /src TB --- 2013-05-10 23:38:56 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:38:56 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-11 00:19:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-11 00:19:36 - ERROR: failed to build world TB --- 2013-05-11 00:19:36 - 2036.98 user 363.34 system 2443.49 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[releng_8 tinderbox] failure on powerpc/powerpc
TB --- 2013-05-10 23:38:23 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-05-10 23:38:23 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-05-10 23:38:23 - starting RELENG_8 tinderbox run for powerpc/powerpc TB --- 2013-05-10 23:38:23 - cleaning the object tree TB --- 2013-05-10 23:38:23 - /usr/local/bin/svn stat /src TB --- 2013-05-10 23:38:25 - At svn revision 250487 TB --- 2013-05-10 23:38:26 - building world TB --- 2013-05-10 23:38:26 - CROSS_BUILD_TESTING=YES TB --- 2013-05-10 23:38:26 - MAKEOBJDIRPREFIX=/obj TB --- 2013-05-10 23:38:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-05-10 23:38:26 - SRCCONF=/dev/null TB --- 2013-05-10 23:38:26 - TARGET=powerpc TB --- 2013-05-10 23:38:26 - TARGET_ARCH=powerpc TB --- 2013-05-10 23:38:26 - TZ=UTC TB --- 2013-05-10 23:38:26 - __MAKE_CONF=/dev/null TB --- 2013-05-10 23:38:26 - cd /src TB --- 2013-05-10 23:38:26 - /usr/bin/make -B buildworld >>> World build started on Fri May 10 23:38:27 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz ===> usr.sbin/newsyslog (all) cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c cc1: warnings being treated as errors /src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog': /src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid' *** [newsyslog.o] Error code 1 Stop in /src/usr.sbin/newsyslog. *** [all] Error code 1 Stop in /src/usr.sbin. *** [usr.sbin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** [buildworld] Error code 1 Stop in /src. TB --- 2013-05-11 00:21:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-05-11 00:21:02 - ERROR: failed to build world TB --- 2013-05-11 00:21:02 - 2160.27 user 369.84 system 2559.17 real http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-powerpc-powerpc.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
How abuot firewall_nat_rules?
Hi stable list,
Now ipfw_nat's rules must be write directly in firewall_nat_flags. This is
messy to describe many rules. firewall_nat_rules will be treat smartly.
To enable firewall_nat_rules,apply following patch to /etc/rc.firewall
--- /etc/rc.firewall.org2013-05-11 08:23:13.0 +0900
+++ /etc/rc.firewall2013-05-11 08:29:11.0 +0900
@@ -162,6 +162,9 @@
case ${firewall_nat_enable} in
[Yy][Ee][Ss])
if [ -n "${firewall_nat_interface}" ]; then
+ if [ -r "${firewall_nat_rules}" ]; then
+ firewall_nat_flags="${firewall_nat_flags} `cat
${firewall_nat_rules}`"
+ fi
if echo "${firewall_nat_interface}" | \
grep -q -E '^[0-9]+(\.[0-9]+){0,3}$'; then
firewall_nat_flags="ip
${firewall_nat_interface} ${firewall_nat_flags}"
and then put in /etc/rc.conf
firewall_enable="YES"
firewall_type="OPEN"
firewall_nat_enable="YES"
firewall_nat_interface="X.X.X.X"
firewall_nat_flags="deny_in reset same_ports unreg_only"
firewall_nat_rules="/etc/ipfw_nat.rules"
where X.X.X.X is the outgoing global address and firewall_nat_rules specfies
the file in which describe ipfw_nat's rules, actually ipfw arguments
following to "${fwcmd} nat 123 config log" for example
redirect_port tcp 192.168.1.7:24012401
redirect_port tcp 192.168.1.5:80 80
redirect_port tcp 192.168.1.1:22 22069
redirect_port tcp 192.168.1.2:22 22053
redirect_port tcp 192.168.1.3:22 22025
redirect_port tcp 192.168.1.4:22 22080
redirect_port tcp 192.168.1.5:22 22021
redirect_port tcp 192.168.1.6:22 22067
redirect_port tcp 192.168.1.7:22 22401
redirect_port tcp 192.168.1.8:22 22081
redirect_port tcp 192.168.1.32:9100 63189
redirect_port tcp 192.168.1.252:9100 23089
redirect_port tcp 192.168.1.254:2222
Regards
---
k...@openedu.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
