[head tinderbox] failure on mips/mips
TB --- 2012-03-30 04:37:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-30 04:37:00 - starting HEAD tinderbox run for mips/mips TB --- 2012-03-30 04:37:00 - cleaning the object tree TB --- 2012-03-30 04:37:42 - cvsupping the source tree TB --- 2012-03-30 04:37:42 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2012-03-30 04:38:31 - building world TB --- 2012-03-30 04:38:31 - CROSS_BUILD_TESTING=YES TB --- 2012-03-30 04:38:31 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-30 04:38:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-30 04:38:31 - SRCCONF=/dev/null TB --- 2012-03-30 04:38:31 - TARGET=mips TB --- 2012-03-30 04:38:31 - TARGET_ARCH=mips TB --- 2012-03-30 04:38:31 - TZ=UTC TB --- 2012-03-30 04:38:31 - __MAKE_CONF=/dev/null TB --- 2012-03-30 04:38:31 - cd /src TB --- 2012-03-30 04:38:31 - /usr/bin/make -B buildworld >>> World build started on Fri Mar 30 04:38:31 UTC 2012 >>> 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 -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -c /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -o kfd kfd.o -lkrb5 -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kfd/../../lib/libvers/libvers.a gzip -cn /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.8 > kfd.8.gz ===> kerberos5/libexec/kimpersonate (all) cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -c /src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/kuser/kimpersonate.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -o kimpersonate kimpersonate.o -lkafs5 -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kimpersonate/../../lib/libvers/libvers.a /obj/mips.mips/src/tmp/usr/bin/ld: /obj/mips.mips/src/tmp/usr/lib/libkafs5.so symbol number 13 references nonexistent SHT_SYMTAB_SHNDX section /obj/mips.mips/src/tmp/usr/lib/libkafs5.so: could not read symbols: File format not recognized *** Error code 1 Stop in /src/kerberos5/libexec/kimpersonate. *** Error code 1 Stop in /src/kerberos5/libexec. *** Error code 1 Stop in /src/kerberos5. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-30 05:27:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-30 05:27:06 - ERROR: failed to build world TB --- 2012-03-30 05:27:06 - 2084.06 user 431.77 system 3006.22 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full ___ 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"
[head tinderbox] failure on mips/mips
TB --- 2012-03-29 20:22:47 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 20:22:47 - starting HEAD tinderbox run for mips/mips TB --- 2012-03-29 20:22:47 - cleaning the object tree TB --- 2012-03-29 20:23:56 - cvsupping the source tree TB --- 2012-03-29 20:23:56 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2012-03-29 20:25:02 - building world TB --- 2012-03-29 20:25:02 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 20:25:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 20:25:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 20:25:02 - SRCCONF=/dev/null TB --- 2012-03-29 20:25:02 - TARGET=mips TB --- 2012-03-29 20:25:02 - TARGET_ARCH=mips TB --- 2012-03-29 20:25:02 - TZ=UTC TB --- 2012-03-29 20:25:02 - __MAKE_CONF=/dev/null TB --- 2012-03-29 20:25:02 - cd /src TB --- 2012-03-29 20:25:02 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 20:25:03 UTC 2012 >>> 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 -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -c /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -o kfd kfd.o -lkrb5 -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kfd/../../lib/libvers/libvers.a gzip -cn /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.8 > kfd.8.gz ===> kerberos5/libexec/kimpersonate (all) cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -c /src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/kuser/kimpersonate.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -o kimpersonate kimpersonate.o -lkafs5 -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kimpersonate/../../lib/libvers/libvers.a /obj/mips.mips/src/tmp/usr/bin/ld: /obj/mips.mips/src/tmp/usr/lib/libkafs5.so symbol number 13 references nonexistent SHT_SYMTAB_SHNDX section /obj/mips.mips/src/tmp/usr/lib/libkafs5.so: could not read symbols: File format not recognized *** Error code 1 Stop in /src/kerberos5/libexec/kimpersonate. *** Error code 1 Stop in /src/kerberos5/libexec. *** Error code 1 Stop in /src/kerberos5. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 21:13:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 21:13:47 - ERROR: failed to build world TB --- 2012-03-29 21:13:47 - 2101.02 user 446.11 system 3059.83 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full ___ 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: Using TMPFS for /tmp and /var/run?
On 03/29/2012 14:58, David Wolfskill wrote: On Thu, Mar 29, 2012 at 02:50:00PM -0500, Eric van Gyzen wrote: ... However, if you always want to use tmpfs instead of stable storage, please do not. Some people expect /tmp to be persistent. This is why /etc/defaults/rc.conf has clear_tmp_enable="NO". Changing this would break the POLA. ... Errr... I'm not sure why folks might have that misguided expectation; Because that's how the default installation has behaved for a long time. I'm not saying this expectation is /wise/; I'm just saying some people have formed that expectation by observing the behavior of the default system, and they would be astonished by this change. from hier(7): /tmp/ temporary files that are not guaranteed to persist across sys- tem reboots Foplks are welcome to do whatever they wish with their own machines, but the FreeBSD default is as above. Respectfully, no. The default is to store /tmp in UFS, either in its own partition (with Auto Defaults) or in / (if no partition was created for it), and to refrain from clearing it at boot. Thus, although /tmp is not guaranteed to persist in theory, it is rather persistent in practice. My only point is: carefully consider the change in behavior of the default installation before breaking the POLA. Eric ___ 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: Using TMPFS for /tmp and /var/run?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/29/12 09:41, Chris Rees wrote: > On 29 Mar 2012 16:49, "O. Hartmann" > wrote: >> >> I was wondering if there are some objections using TMPFS for /tmp >> and /var/run. I figured out some problems with some rc.d scripts >> when using TMPFS for /var/run, samba and OpenLDAP do store some >> informations like PID in a subfolder of their own in /var/run, >> but the rc.d scripts are not checking properly the existence of >> the appropritae folder (unlike "dbus" and "hald", they check >> properly!). >> >> I already submitted two PRs, but for SAMBA, my "hack" is trivial >> and obviously to clumsy, so it should be check properly. >> >> My question is whether there are objections using TMPFS for bot >> /tmp/ and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? > > Any rc script that complains about an empty /var/run is buggy- it > should be assumed that it will be emptied on boot. Agreed. We may want a generic way of registering custom mtrees (or something) that creates the hierarchy on boot, by the way. Currently this has to be done by individual rc.d scripts if they need a separate directory. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPdMuiAAoJEG80Jeu8UPuzJKsH/js4Fsvb/drjTFGRwmOmSJ5V 7lfVxT6cuFTB1vpCTooR2rVzxZyfqSzeFwc5i8lbhK8+SA13Q46jkCZyHQCgoEqX n2ZIIMgIi+04+IQGrA9742Rkd/7RtvD88xf1wXcgkoY9IImpaYLvjVfcxMqxYMvI 75OHIsmvIbxt/vnmVx26Omh3ZvvHN2QI8n6lUqjqWVm96qEGwdoBuA+m2g5QKem/ 24gLZ0kttmO/zKo8vKRTgR9RiCYeS2IUueLy4PDmMKf8Oiv3/Y9f3c8S8Bw4qVdB cOKqugBtInCu3BnsPrDJpoNUiSb+Cf5aLggbPSocD9A1iToChDmyRF5eC6Tc6Kw= =owJ7 -END PGP SIGNATURE- ___ 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: Using TMPFS for /tmp and /var/run?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/29/12 09:59, Vitaly Magerya wrote:
> Chris Rees wrote:
>> Any rc script that complains about an empty /var/run is buggy- it
>> should be assumed that it will be emptied on boot.
>
> Then why are there entries for /var/run/{named,ppp,wpa_supplicant}
> in /etc/mtree/BSD.var.dist? Should they be removed?
No, they are populated by /etc/rc.d/var...
Cheers,
- --
Xin LI https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAEBCAAGBQJPdMsBAAoJEG80Jeu8UPuzug4H/joM719VK0TeISLSRusdcdnQ
9k0VnmuBtxUgzh+Wrsb/Ka5jROg39+hVLHKEIszMrZ1Ip85YW4JpnL1cq2OJ+ZKV
dXFt8b8KVPcO0XBMAnvaD8x7J9emrNQU54VMhumAun+IpyGXTvATBCPaPB5zewMJ
DAai5rSXi/jOdjdXmgxydtRsaXdwR4dHlQ/EPmpby9pnxEwqRjQHkl4ZvTYC0yNU
+UCffIqbQsn/Zerwxzg9NnTSjVDKNgN192xhsDJN9hXDAFro1aG2LMSA4iYPxsYH
ge0P6cO21qb7fRDB6KdHB/qUF1zcTt9cw+IsWKmBV3qN+GkDiB7vtKJa7hX/1XE=
=3B8C
-END PGP SIGNATURE-
___
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: NEWS: NVIDIA Open-Sources Its CUDA Compiler
В Thu, 15 Dec 2011 01:02:03 +0100 "O. Hartmann" пишет: > Just read this on > > phoronix.com > > Is this finally a chance to get GPGPU on FreeBSD natively supported? > > nVidia has a binary driver, supporting well their higher end graphics > cards on FreeBSD 64bit natively. > > I do not understand much about the compiler itself, it's "nvcc" as far > as I know, and it is also doing well OpenCL (with some serious bugs we > revealed). > > What would be needed to bring FreeBSd finally back to the HPC scenario > with being capable of dealing natively with GPGPU stuff on nVidia > graphics cards? There are libraries installed by the driver or the > SDK. With a OpenSource compiler it should also be possible for nVidia, > assumed the compiler works with freeBSD natively, to provide OpenCL > stuff as well as CUDA stuff. > Please correct me and destroy me "dreams" having FreeBSD in my lab > working on GPUs ... > > The decission sounds like some pitfall in a contract. Is nVidia > dropping CUDA in favour of OpenCL or is the CUDA compiler only a tiny > piece of the whole thing that could be easily considered open source > without changing the "great restricted Linux-only" picture? > > Maybe LLVM, now part of FreeBSD's backbone, is capable of taking > advantage of the opening of the CUDA compiler so we will see a > combination of CLANG/OpenCL/CUDA soon on FreeBSD introduced by LLVM? > > Well, well, this is awesome ... ;-) > > Oliver > Perhaps it will interest yous http://runtime.bordeaux.inria.fr/StarPU/ Just tried it - excellent build from source code in FreeBSD CURRENT. ___ 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: Using TMPFS for /tmp and /var/run?
On Thu, Mar 29, 2012 at 10:07:01PM +0200, O. Hartmann wrote: > ... > Aren't MDMFS backed filesystems of static size? And haven't they to be > created first before they can be used? Using TMPFS seems toi be a more > convenient way to me - dynamical (?), using a fstab entry for convenience. One may create a swap-backed mfs; this is what I used to do for /tmp before I started using tmpfs. (See the "tmpmfs" line (and related lines) in /etc/defaults/rc.conf.) >... Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpbMAzxZUI37.pgp Description: PGP signature
Re: Using TMPFS for /tmp and /var/run?
Am 03/29/12 21:50, schrieb Eric van Gyzen: > On 03/29/12 09:18, O. Hartmann wrote: >> I was wondering if there are some objections using TMPFS for /tmp and >> /var/run. > > For /tmp, what exactly do you mean? > > If you want to use tmpfs instead of md/mdmfs when tmpmfs="YES" in > rc.conf, I have no opinion. Aren't MDMFS backed filesystems of static size? And haven't they to be created first before they can be used? Using TMPFS seems toi be a more convenient way to me - dynamical (?), using a fstab entry for convenience. > > However, if you always want to use tmpfs instead of stable storage, > please do not. Some people expect /tmp to be persistent. This is why > /etc/defaults/rc.conf has clear_tmp_enable="NO". Changing this would > break the POLA. > > Cheers, > > Eric I have set clear_tmp_enable="YES". I treat /tmp as it is: temporary. No one should change the default setting. Well, SSDs become more and more popular, even for heavy duty servers. Still facing the waer-off problemacy with NAND flash memory, I'd would feel better have the main memory used by the volatile filesystems like /var/run and /tmp which get rewritten quite often. signature.asc Description: OpenPGP digital signature
Re: Using TMPFS for /tmp and /var/run?
On Thu, Mar 29, 2012 at 02:50:00PM -0500, Eric van Gyzen wrote: > ... > However, if you always want to use tmpfs instead of stable storage, > please do not. Some people expect /tmp to be persistent. This is why > /etc/defaults/rc.conf has clear_tmp_enable="NO". Changing this would > break the POLA. > ... Errr... I'm not sure why folks might have that misguided expectation; from hier(7): /tmp/ temporary files that are not guaranteed to persist across sys- tem reboots Foplks are welcome to do whatever they wish with their own machines, but the FreeBSD default is as above. And I was using swap-backed /tmp on SunOS back around 1988 :-} Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpQSUcQ0Mxkt.pgp Description: PGP signature
Re: Using TMPFS for /tmp and /var/run?
On 03/29/12 09:18, O. Hartmann wrote: I was wondering if there are some objections using TMPFS for /tmp and /var/run. For /tmp, what exactly do you mean? If you want to use tmpfs instead of md/mdmfs when tmpmfs="YES" in rc.conf, I have no opinion. However, if you always want to use tmpfs instead of stable storage, please do not. Some people expect /tmp to be persistent. This is why /etc/defaults/rc.conf has clear_tmp_enable="NO". Changing this would break the POLA. Cheers, Eric ___ 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: Using TMPFS for /tmp and /var/run?
Am 03/29/12 18:14, schrieb David Wolfskill: > On Thu, Mar 29, 2012 at 04:18:06PM +0200, O. Hartmann wrote: >> I was wondering if there are some objections using TMPFS for /tmp and >> /var/run. >> ... >> My question is whether there are objections using TMPFS for bot /tmp/ >> and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? >> > > I have no experience using tmpfs for /var/run, but I have been using it > for /tmp for some time (mostly in i386, though). > > While I use it quite successfully on machines with a small number of > folks actively busy -- e.g., my desktop; my laptop; my home machines), I > encountered some issues when I tried to do so on machines that were > intended for significantly "heavier" use. Specifically: > > * Compared to an md-resident /tmp, a tmpfs-resident /tmp has much less > flexibility for specifying the size. Per mdconfig(8), the former > uses: > > -s size > Size of the memory disk. Size is the number of 512 byte sectors > unless suffixed with a b, k, m, g, or t which denotes byte, kilo- > byte, megabyte, gigabyte and terabyte respectively. Options -a > and -t swap are implied if not specified. > > while the latter uses: > > sizeSpecifies the total file system size in bytes. If zero (the > default) or a value larger than SIZE_MAX - PAGE_SIZE is given, > the available amount of memory (including main memory and swap > space) will be used. > > In this configuration, I would have preferred to have specified > about 10GB for /tmp. I wouldn't mind if it spilled to swap space, > but I certaianly didn't want it using 10GB of RAM -- especially since > the machines only had 6GB RAM. > > Nor did I especially want *all* of the swap space used for /tmp. I > would have allocated (say) 20GB for swap. I wouldn't mind if half of > that were used for /tmp -- but a reason I allocate so much swap is > that I've seen what happens when a machine runs out of swap, and it > wasn't pretty. > > > In any case, effective maximum usable size for tmpfs involves SIZE_MAX > (~4G) & PAGE_SIZE (4K, in my case). > > * Even when I went ahead and created a tmpfs for /tmp, I'd get ENOSPC > whenever I tried to allocate anything on it -- until I dropped the > size specification to <2G (2**32). Well, 2GB for /tmp just wasn't at > all likely to be useful for my purposes in this case. > > So I continue to use tmpfs for /tmp for machines with fewer folks > logging in, but I'm a bit less enthusiastic about its use unless the > workload and other requirements are fairly carefully considered > beforehand. > > Peace, > david It seems there is only one switch which determines the size of the tmpfs in question (size) and there is no convenient way to say what amount of RAM is being used before using the swap space. I'd like to have at least a knob determining the limit of RAM being used. On the other hand - my view of those things is really naiv. I think having tmpfs isn't even a benefit in terms of security, it should also offer a speedy access to files kept in memory, doesn't it? Linux is using TMPFS filesystems a lot for these purposes. How do they overcome restrictions of the size or not flloding RAM and/or swap? Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: Using TMPFS for /tmp and /var/run?
Chris Rees wrote:
> Any rc script that complains about an empty /var/run is buggy- it should be
> assumed that it will be emptied on boot.
Then why are there entries for /var/run/{named,ppp,wpa_supplicant}
in /etc/mtree/BSD.var.dist? Should they be removed?
___
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: Using TMPFS for /tmp and /var/run?
On 29 Mar 2012 16:49, "O. Hartmann" wrote: > > I was wondering if there are some objections using TMPFS for /tmp and > /var/run. > I figured out some problems with some rc.d scripts when using TMPFS for > /var/run, samba and OpenLDAP do store some informations like PID in a > subfolder of their own in /var/run, but the rc.d scripts are not > checking properly the existence of the appropritae folder (unlike "dbus" > and "hald", they check properly!). > > I already submitted two PRs, but for SAMBA, my "hack" is trivial and > obviously to clumsy, so it should be check properly. > > My question is whether there are objections using TMPFS for bot /tmp/ > and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? Any rc script that complains about an empty /var/run is buggy- it should be assumed that it will be emptied on boot. In short, tmpfs for those two dirs should be fine. Chris ___ 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: Using TMPFS for /tmp and /var/run?
On Thu, Mar 29, 2012 at 04:18:06PM +0200, O. Hartmann wrote: > I was wondering if there are some objections using TMPFS for /tmp and > /var/run. > ... > My question is whether there are objections using TMPFS for bot /tmp/ > and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? > I have no experience using tmpfs for /var/run, but I have been using it for /tmp for some time (mostly in i386, though). While I use it quite successfully on machines with a small number of folks actively busy -- e.g., my desktop; my laptop; my home machines), I encountered some issues when I tried to do so on machines that were intended for significantly "heavier" use. Specifically: * Compared to an md-resident /tmp, a tmpfs-resident /tmp has much less flexibility for specifying the size. Per mdconfig(8), the former uses: -s size Size of the memory disk. Size is the number of 512 byte sectors unless suffixed with a b, k, m, g, or t which denotes byte, kilo- byte, megabyte, gigabyte and terabyte respectively. Options -a and -t swap are implied if not specified. while the latter uses: sizeSpecifies the total file system size in bytes. If zero (the default) or a value larger than SIZE_MAX - PAGE_SIZE is given, the available amount of memory (including main memory and swap space) will be used. In this configuration, I would have preferred to have specified about 10GB for /tmp. I wouldn't mind if it spilled to swap space, but I certaianly didn't want it using 10GB of RAM -- especially since the machines only had 6GB RAM. Nor did I especially want *all* of the swap space used for /tmp. I would have allocated (say) 20GB for swap. I wouldn't mind if half of that were used for /tmp -- but a reason I allocate so much swap is that I've seen what happens when a machine runs out of swap, and it wasn't pretty. In any case, effective maximum usable size for tmpfs involves SIZE_MAX (~4G) & PAGE_SIZE (4K, in my case). * Even when I went ahead and created a tmpfs for /tmp, I'd get ENOSPC whenever I tried to allocate anything on it -- until I dropped the size specification to <2G (2**32). Well, 2GB for /tmp just wasn't at all likely to be useful for my purposes in this case. So I continue to use tmpfs for /tmp for machines with fewer folks logging in, but I'm a bit less enthusiastic about its use unless the workload and other requirements are fairly carefully considered beforehand. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgppDfe0Vfs6f.pgp Description: PGP signature
[head tinderbox] failure on powerpc64/powerpc
TB --- 2012-03-29 14:06:55 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 14:06:55 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-03-29 14:06:55 - cleaning the object tree TB --- 2012-03-29 14:07:46 - cvsupping the source tree TB --- 2012-03-29 14:07:47 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-03-29 14:08:19 - building world TB --- 2012-03-29 14:08:19 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 14:08:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 14:08:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 14:08:19 - SRCCONF=/dev/null TB --- 2012-03-29 14:08:19 - TARGET=powerpc TB --- 2012-03-29 14:08:19 - TARGET_ARCH=powerpc64 TB --- 2012-03-29 14:08:19 - TZ=UTC TB --- 2012-03-29 14:08:19 - __MAKE_CONF=/dev/null TB --- 2012-03-29 14:08:19 - cd /src TB --- 2012-03-29 14:08:19 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 14:08:20 UTC 2012 >>> 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 [...] gzip -cn /src/sys/boot/powerpc/ofw/../../forth/version.4th.8 > version.4th.8.gz gzip -cn /src/sys/boot/powerpc/ofw/../../common/loader.8 > loader.8.gz cat /src/sys/boot/powerpc/ofw/../../common/help.common /src/sys/boot/powerpc/ofw/help.ofw | awk -f /src/sys/boot/powerpc/ofw/../../common/merge_help.awk > loader.help ===> sys/boot/powerpc/ps3 (all) cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_EXT2FS_SUPPORT -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/powerpc/ps3/../../ficl -I/src/sys/boot/powerpc/ps3/../../ficl/powerpc -DNETIF_OPEN_CLOSE_ONCE -mcpu=powerpc64 -I/src/sys/boot/powerpc/ps3/../../common -I/src/sys/boot/powerpc/ps3/../../.. -I. -Wall -ffreestanding -msoft-float -DAIM -DRELOC=0x0 -Wa,-mppc64bridge -I/src/sys/boot/powerpc/ps3/../../../../lib/libstand/ -m32 -mcpu=powerpc -std=gnu99 -c /src/sys/boot/powerpc/ps3/start.S /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h: Assembler messages: /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h:123: Error: Unrecognized opcode: `struct' /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h:124: Error: Unrecognized opcode: `void' *** Error code 1 Stop in /src/sys/boot/powerpc/ps3. *** Error code 1 Stop in /src/sys/boot/powerpc. *** Error code 1 Stop in /src/sys/boot. *** Error code 1 Stop in /src/sys. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 16:12:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 16:12:28 - ERROR: failed to build world TB --- 2012-03-29 16:12:28 - 6039.50 user 763.22 system 7532.84 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full ___ 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"
Boot-issue: Overlapping I/O regions and display adapters in -current
Hi, It appears that overlapping I/O regions can trigger a bug on display adapters, which I've tried to fix here: http://svn.freebsd.org/changeset/base/233662 I'm not an expert in this area, though if anyone has any better suggestions, I am willing to try that. Sympthom: ACPI enabled i386 kernel works, ACPI enabled amd64 kernel stops during boot due to invalid CPU instruction exactly after disabling BAR on AGP device. --HPS ___ 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"
Using TMPFS for /tmp and /var/run?
I was wondering if there are some objections using TMPFS for /tmp and /var/run. I figured out some problems with some rc.d scripts when using TMPFS for /var/run, samba and OpenLDAP do store some informations like PID in a subfolder of their own in /var/run, but the rc.d scripts are not checking properly the existence of the appropritae folder (unlike "dbus" and "hald", they check properly!). I already submitted two PRs, but for SAMBA, my "hack" is trivial and obviously to clumsy, so it should be check properly. My question is whether there are objections using TMPFS for bot /tmp/ and /var/run/ at this stage on FreeBSD 10.0-CURRENT/amd64? Regards, Oliver signature.asc Description: OpenPGP digital signature
[head tinderbox] failure on powerpc/powerpc
TB --- 2012-03-29 13:15:34 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 13:15:34 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-03-29 13:15:34 - cleaning the object tree TB --- 2012-03-29 13:17:57 - cvsupping the source tree TB --- 2012-03-29 13:17:57 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-03-29 13:19:22 - building world TB --- 2012-03-29 13:19:22 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 13:19:22 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 13:19:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 13:19:22 - SRCCONF=/dev/null TB --- 2012-03-29 13:19:22 - TARGET=powerpc TB --- 2012-03-29 13:19:22 - TARGET_ARCH=powerpc TB --- 2012-03-29 13:19:22 - TZ=UTC TB --- 2012-03-29 13:19:22 - __MAKE_CONF=/dev/null TB --- 2012-03-29 13:19:22 - cd /src TB --- 2012-03-29 13:19:22 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 13:19:23 UTC 2012 >>> 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 [...] gzip -cn /src/sys/boot/powerpc/ofw/../../forth/version.4th.8 > version.4th.8.gz gzip -cn /src/sys/boot/powerpc/ofw/../../common/loader.8 > loader.8.gz cat /src/sys/boot/powerpc/ofw/../../common/help.common /src/sys/boot/powerpc/ofw/help.ofw | awk -f /src/sys/boot/powerpc/ofw/../../common/merge_help.awk > loader.help ===> sys/boot/powerpc/ps3 (all) cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_EXT2FS_SUPPORT -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/powerpc/ps3/../../ficl -I/src/sys/boot/powerpc/ps3/../../ficl/powerpc -DNETIF_OPEN_CLOSE_ONCE -mcpu=powerpc64 -I/src/sys/boot/powerpc/ps3/../../common -I/src/sys/boot/powerpc/ps3/../../.. -I. -Wall -ffreestanding -msoft-float -DAIM -DRELOC=0x0 -Wa,-mppc64bridge -I/src/sys/boot/powerpc/ps3/../../../../lib/libstand/ -std=gnu99 -c /src/sys/boot/powerpc/ps3/start.S /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h: Assembler messages: /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h:123: Error: Unrecognized opcode: `struct' /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h:124: Error: Unrecognized opcode: `void' *** Error code 1 Stop in /src/sys/boot/powerpc/ps3. *** Error code 1 Stop in /src/sys/boot/powerpc. *** Error code 1 Stop in /src/sys/boot. *** Error code 1 Stop in /src/sys. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 15:21:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 15:21:57 - ERROR: failed to build world TB --- 2012-03-29 15:21:57 - 5991.83 user 770.28 system 7582.68 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full ___ 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"
[head tinderbox] failure on mips/mips
TB --- 2012-03-29 13:15:11 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 13:15:11 - starting HEAD tinderbox run for mips/mips TB --- 2012-03-29 13:15:11 - cleaning the object tree TB --- 2012-03-29 13:16:16 - cvsupping the source tree TB --- 2012-03-29 13:16:16 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2012-03-29 13:17:16 - building world TB --- 2012-03-29 13:17:16 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 13:17:16 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 13:17:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 13:17:16 - SRCCONF=/dev/null TB --- 2012-03-29 13:17:16 - TARGET=mips TB --- 2012-03-29 13:17:16 - TARGET_ARCH=mips TB --- 2012-03-29 13:17:16 - TZ=UTC TB --- 2012-03-29 13:17:16 - __MAKE_CONF=/dev/null TB --- 2012-03-29 13:17:16 - cd /src TB --- 2012-03-29 13:17:16 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 13:17:17 UTC 2012 >>> 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 -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -c /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kfd/../../../crypto/heimdal/lib/roken -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kfd/../../include -std=gnu99 -o kfd kfd.o -lkrb5 -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kfd/../../lib/libvers/libvers.a gzip -cn /src/kerberos5/libexec/kfd/../../../crypto/heimdal/appl/kf/kfd.8 > kfd.8.gz ===> kerberos5/libexec/kimpersonate (all) cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -c /src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/kuser/kimpersonate.c cc -O -pipe -G0 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/hx509 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/roken -I/src/kerberos5/libexec/kimpersonate/../../../crypto/heimdal/lib/sl -I. -DHAVE_CONFIG_H -I/src/kerberos5/libexec/kimpersonate/../../include -std=gnu99 -o kimpersonate kimpersonate.o -lkafs5 -lkrb5 -lheimntlm -lroken -lasn1 -lcrypto -lcrypt /obj/mips.mips/src/kerberos5/libexec/kimpersonate/../../lib/libvers/libvers.a /obj/mips.mips/src/tmp/usr/bin/ld: /obj/mips.mips/src/tmp/usr/lib/libkafs5.so symbol number 13 references nonexistent SHT_SYMTAB_SHNDX section /obj/mips.mips/src/tmp/usr/lib/libkafs5.so: could not read symbols: File format not recognized *** Error code 1 Stop in /src/kerberos5/libexec/kimpersonate. *** Error code 1 Stop in /src/kerberos5/libexec. *** Error code 1 Stop in /src/kerberos5. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 14:06:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 14:06:55 - ERROR: failed to build world TB --- 2012-03-29 14:06:55 - 2073.02 user 443.07 system 3103.84 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full ___ 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"
[head tinderbox] failure on ia64/ia64
TB --- 2012-03-29 12:23:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 12:23:01 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-03-29 12:23:01 - cleaning the object tree TB --- 2012-03-29 12:23:01 - cvsupping the source tree TB --- 2012-03-29 12:23:01 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-03-29 12:23:53 - building world TB --- 2012-03-29 12:23:53 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 12:23:53 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 12:23:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 12:23:53 - SRCCONF=/dev/null TB --- 2012-03-29 12:23:53 - TARGET=ia64 TB --- 2012-03-29 12:23:53 - TARGET_ARCH=ia64 TB --- 2012-03-29 12:23:53 - TZ=UTC TB --- 2012-03-29 12:23:53 - __MAKE_CONF=/dev/null TB --- 2012-03-29 12:23:53 - cd /src TB --- 2012-03-29 12:23:53 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 12:23:54 UTC 2012 >>> 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 -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/ia64 -I/src/libexec/rtld-elf -fpic -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/rtld.c /src/libexec/rtld-elf/rtld.c: In function 'do_dlsym': /src/libexec/rtld-elf/rtld.c:2621: error: 'tls_index' undeclared (first use in this function) /src/libexec/rtld-elf/rtld.c:2621: error: (Each undeclared identifier is reported only once /src/libexec/rtld-elf/rtld.c:2621: error: for each function it appears in.) /src/libexec/rtld-elf/rtld.c:2621: error: expected ';' before 'ti' /src/libexec/rtld-elf/rtld.c:2737: error: 'ti' undeclared (first use in this function) /src/libexec/rtld-elf/rtld.c:2739: error: too few arguments to function '__tls_get_addr' *** Error code 1 Stop in /src/libexec/rtld-elf. *** Error code 1 Stop in /src/libexec. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 13:15:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 13:15:34 - ERROR: failed to build world TB --- 2012-03-29 13:15:34 - 2224.05 user 415.48 system 3152.70 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ 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"
[head tinderbox] failure on powerpc64/powerpc
TB --- 2012-03-29 06:59:43 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 06:59:43 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-03-29 06:59:43 - cleaning the object tree TB --- 2012-03-29 07:01:26 - cvsupping the source tree TB --- 2012-03-29 07:01:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-03-29 07:02:16 - building world TB --- 2012-03-29 07:02:16 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 07:02:16 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 07:02:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 07:02:16 - SRCCONF=/dev/null TB --- 2012-03-29 07:02:16 - TARGET=powerpc TB --- 2012-03-29 07:02:16 - TARGET_ARCH=powerpc64 TB --- 2012-03-29 07:02:16 - TZ=UTC TB --- 2012-03-29 07:02:16 - __MAKE_CONF=/dev/null TB --- 2012-03-29 07:02:16 - cd /src TB --- 2012-03-29 07:02:16 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 07:02:17 UTC 2012 >>> 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 [...] gzip -cn /src/sys/boot/powerpc/ofw/../../forth/version.4th.8 > version.4th.8.gz gzip -cn /src/sys/boot/powerpc/ofw/../../common/loader.8 > loader.8.gz cat /src/sys/boot/powerpc/ofw/../../common/help.common /src/sys/boot/powerpc/ofw/help.ofw | awk -f /src/sys/boot/powerpc/ofw/../../common/merge_help.awk > loader.help ===> sys/boot/powerpc/ps3 (all) cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_EXT2FS_SUPPORT -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/powerpc/ps3/../../ficl -I/src/sys/boot/powerpc/ps3/../../ficl/powerpc -DNETIF_OPEN_CLOSE_ONCE -mcpu=powerpc64 -I/src/sys/boot/powerpc/ps3/../../common -I/src/sys/boot/powerpc/ps3/../../.. -I. -Wall -ffreestanding -msoft-float -DAIM -DRELOC=0x0 -Wa,-mppc64bridge -I/src/sys/boot/powerpc/ps3/../../../../lib/libstand/ -m32 -mcpu=powerpc -std=gnu99 -c /src/sys/boot/powerpc/ps3/start.S /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h: Assembler messages: /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h:123: Error: Unrecognized opcode: `struct' /obj/powerpc.powerpc64/src/tmp/usr/include/machine/trap_aim.h:124: Error: Unrecognized opcode: `void' *** Error code 1 Stop in /src/sys/boot/powerpc/ps3. *** Error code 1 Stop in /src/sys/boot/powerpc. *** Error code 1 Stop in /src/sys/boot. *** Error code 1 Stop in /src/sys. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 09:01:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 09:01:47 - ERROR: failed to build world TB --- 2012-03-29 09:01:47 - 5865.80 user 709.23 system 7324.67 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full ___ 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: PostgreSQL server 9.1.3 rejects connections after update: Error connection to the server: FATAL: frontend-protocol 1234.5887 not supported: server supports 1.0 through 3.0
Am 03/27/12 15:20, schrieb Eduardo Morras: > At 10:54 27/03/2012, you wrote: >> Since the last PostgreSQL port update, server and client are version >> 9.1.3 and a newly build of the FreeBSD OS (both 9.0-STABLE and >> 10.0-CURRENT, amd64), clients like pgadmin3 or webinterfaces like those >> from refdb reject connection to the PostgreSQL server with the error >> message: >> >> Error connection to the server: FATAL: frontend-protocol 1234.5887 not >> supported: server supports 1.0 through 3.0 >> >> All users, execept a local admin and the psql user, are kept in >> OpenLDAP. It seems, that the LDAP connection got messed up somehow. >> >> I tried to recompile everything required by OpenLDAP, PostgreSQL via >> >> portmaster -f, since I realized changes in Heimdal on FreeBSD 10.0-CUR >> and I deleted the old libs via delete-old-libs/files. >> >> Does anyone see this problem, too? > > No sorry, i use 8.2 for Postgresql server. > > Have you touched the pg_hba.conf file? Perhaps it has been reinstalled > and setted with default values, so pg don't know what a ldap server is. As I figured out, this problem occurs only with clients running on FreeBSD 10.0-CURRENT. A notebook, FreeBSD 9.0/amd64, but with most recent ports, also postgresql-9.1.3 clients, recompiled textproc/refdb clients, recompiled openldap clients, recompiled pgadmin3 (and all the dependencies) does not sho this weird error and behaviour. As I wrote, the configs of the server hasn't been touched, ran perfectly since approx. a week ago even with the FreeBSD 10 clients and now, after a recent update (do not know whether a port or OS triggers the problem) I receive this weird behaviour which is really boring. As far as I know, there was a Kerberos5/Heimdal update recently on FreeBSD 10. I did a "make delete-old-*" in /usr/src and deleted those old files/libs/dirs et cetera. After that, I had to recompile a bunch of ports, even all dependencies of openldap, postgresql, pgadmin and even subversion to make them work again, since the were compiled against those deleted outdated libs in some parts. I can not exactly say that since then the problem occured, but I think it might be that way. Regards, Oliver signature.asc Description: OpenPGP digital signature
[head tinderbox] failure on powerpc/powerpc
TB --- 2012-03-29 06:07:26 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-03-29 06:07:26 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-03-29 06:07:26 - cleaning the object tree TB --- 2012-03-29 06:08:53 - cvsupping the source tree TB --- 2012-03-29 06:08:53 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-03-29 06:09:45 - building world TB --- 2012-03-29 06:09:45 - CROSS_BUILD_TESTING=YES TB --- 2012-03-29 06:09:45 - MAKEOBJDIRPREFIX=/obj TB --- 2012-03-29 06:09:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-03-29 06:09:45 - SRCCONF=/dev/null TB --- 2012-03-29 06:09:45 - TARGET=powerpc TB --- 2012-03-29 06:09:45 - TARGET_ARCH=powerpc TB --- 2012-03-29 06:09:45 - TZ=UTC TB --- 2012-03-29 06:09:45 - __MAKE_CONF=/dev/null TB --- 2012-03-29 06:09:45 - cd /src TB --- 2012-03-29 06:09:45 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 29 06:09:46 UTC 2012 >>> 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 [...] gzip -cn /src/sys/boot/powerpc/ofw/../../forth/version.4th.8 > version.4th.8.gz gzip -cn /src/sys/boot/powerpc/ofw/../../common/loader.8 > loader.8.gz cat /src/sys/boot/powerpc/ofw/../../common/help.common /src/sys/boot/powerpc/ofw/help.ofw | awk -f /src/sys/boot/powerpc/ofw/../../common/merge_help.awk > loader.help ===> sys/boot/powerpc/ps3 (all) cc -O2 -pipe -DLOADER_DISK_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_CD9660_SUPPORT -DLOADER_EXT2FS_SUPPORT -DLOADER_GZIP_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/src/sys/boot/powerpc/ps3/../../ficl -I/src/sys/boot/powerpc/ps3/../../ficl/powerpc -DNETIF_OPEN_CLOSE_ONCE -mcpu=powerpc64 -I/src/sys/boot/powerpc/ps3/../../common -I/src/sys/boot/powerpc/ps3/../../.. -I. -Wall -ffreestanding -msoft-float -DAIM -DRELOC=0x0 -Wa,-mppc64bridge -I/src/sys/boot/powerpc/ps3/../../../../lib/libstand/ -std=gnu99 -c /src/sys/boot/powerpc/ps3/start.S /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h: Assembler messages: /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h:123: Error: Unrecognized opcode: `struct' /obj/powerpc.powerpc/src/tmp/usr/include/machine/trap_aim.h:124: Error: Unrecognized opcode: `void' *** Error code 1 Stop in /src/sys/boot/powerpc/ps3. *** Error code 1 Stop in /src/sys/boot/powerpc. *** Error code 1 Stop in /src/sys/boot. *** Error code 1 Stop in /src/sys. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-03-29 08:14:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-03-29 08:14:17 - ERROR: failed to build world TB --- 2012-03-29 08:14:17 - 6027.37 user 756.51 system 7610.81 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full ___ 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"
