Re: Adding MySQL-5.6 to ports
Jerry ha scritto: I was wondering if anyone was considering adding the development branch MySQL-5.6 to the ports tree? Yes, I'm waiting for the next release. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: postgresql-server-8.4.8_1
13 jun 2011 kl. 20.07 skrev John Bleichert: creating template1 database in /usr/local/pgsql/data/base/1 ... child process was terminated by signal 12: Bad system call initdb: removing contents of data directory /usr/local/pgsql/data $ exit boogie:/var/log uname -a FreeBSD boogie 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Sat Apr 30 02:31:33 EDT 2011 root@boogie:/usr/obj/usr/src/sys/BOOGIE i386 boogie:/var/log pkg_info | grep postgres postgresql-client-8.4.7 PostgreSQL database (client) postgresql-server-8.4.7 The most advanced open-source database available anywhere How did you install the binaries? What is you sysctl -a kern.ipc settings? $ cat /etc/sysctl.conf kern.maxfiles=20 kern.ipc.shm_use_phys=1 kern.ipc.shmmax=8586447872 kern.ipc.shmall=2096301 $ cat /boot/loader.conf kern.ipc.semmni=256 kern.ipc.semmns=512 kern.ipc.semume=40 kern.ipc.semmnu=256 Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: postgresql-server-8.4.8_1
14 jun 2011 kl. 06.34 skrev John Bleichert: On Jun 13, 2011, at 4:31 PM, Christer Solskogen wrote: On Mon, Jun 13, 2011 at 8:07 PM, John Bleichert syb...@earthlink.net wrote: Suggestions? Shall I hit the postgresql forums? I thought I'd ask here first. This is in a jail, right? Try adding this to /etc/sysctl.conf: security.jail.sysvipc_allowed=1 And/or run sysctl security.jail.sysvipc_allowed=1 as root on the host. -- chs, Thanks for getting back to me. No, it's not in a jail. I think there may be something missing in my kernel config - I'm going to try it with the generic FreeBSD 8.2 kernel when I get back to the terminal on Wednesday. For what it's worth I built Postgres 8.4 from source manually and got exactly the same result. OK, then forget first question in previous mail, sorry for not readin the entire thread. Could you perhaps have removed SYSV support in the kernel? $ grep SYS /usr/src/sys/amd64/conf/GENERIC options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Mix Match Southern Africa Holidays
Dear Holiday Fans Herewith 12 great holiday ideas + a selfdrive tour of the Garden Route with 3 optional adventure packages to choose from. If you really want to explore Madagascar then the 12 day 650 km road, canal sea tour is a must. See below . currency conversion A holiday used to be a luxury, however, in today's world, it has become a necessity We offer you Cape Town to Victoria Falls, Madagascar to Zanzibar. Pick Mix and build your Southern Africa HolidayUnable to see the images? Please click here. A collection of 12 great holidays for every occasion, taste, budget and age catered for! Plus 1 of 3 optional self drive Garden Route activity packages to choose from. CAPE TOWN Our price R1376 pp Cape Town Lodge 4 nights BB Min. 2 people sharing ADDO NAT. PARK Our price R1 280.00 pp Zuurberg Mountain Inn 2 nights Half Board SWAZILAND Our price R1995.00 pp Foresters Arms Hotel 3 nights Half Board VICTORIA FALLS Our price R3 847.00 pp The Kingdom Hotel 2 nights fly in package Breakfast daily BIG 5 SAFARI Our price R3 870.00 pp Kapama Buffalo Camp 2 nights All inclusive GORILLA TREKKING Our Price R12 735.00 pp Rwanda 3 nights fly in package Inclusive ZANZIBAR Our price R10 670.00 pp Mapenzi Beach Club 7 nights fly in package Fully Inclusive MADAGASCAR Ile Aux Nattes Beach Our price R6 999.00 pp Le Petite Traversee 7 nights fly in package Breakfast daily MADAGASCAR St Marie Beach Lodge Our price R7805.00 pp Ravoraha Eco Lodge 7 nights fly in package Half Board MADAGASCAR Our price R10603.00 pp Vanila Hotel - Nosy Be 7 nights fly in package Half Board + Excursions MADAGASCAR Our price R13432.00 pp Eden Lodge L'Heure Bleue 7 nights fly in package Half Board MADAGASCAR 12 Day adventure Our price from R13506.00 pp Over 600 Km by Road, Canal Boat, Sea, ending on St Marie Island Your Decide - We Design LOCAL IS LEKKER How about a 2 week self drive holiday along the Garden Route - Cape Town to Port Elizabeth? All organised for you with a choice 1 of 3 inclusive activity packages 13 day Self drive along South Africa's Garden Route - Stellenbosch, Oudtshoorn, Tsitsikamma, Addo National Park, Knysna, Cape Town. Option 1 1. White Shark Cage Diving 2. Tree Top Canopy Tour 3. Hop on off bus tour of the Mother City 4. Cango Wildlife Ranch Option 2 1. Walk a Cheetah 2. Knysna Featherbed Trail Cruise 3. Helicopter Flip over Cape Town 4. Robben Island Tour 5. Cango Wildlife Ranch 6. Monkeyland Birds of Eden tour Option 3 1. Sunset cruise Knysna Lagoon 2. Table Mountain Cable Car 3. Robben Island 4. Helicopter Flip over Cape Town 5. Walk a Cheetah 6. Cango Wildlife Ranch 7.Township tour in Knysna SUBSCRIBE Be the first to know stay up to date with all the Holiday Specials. Please send me your Newsletter of Holiday Specials every two months - CLICK TO JOIN Phone number:086 111 3946 SKYPE phone name:selftourscc Enquiries :e...@selftours.co.za Website :http://www.selftours.co.za Unable to see the images? Please click here. SELFTOURS cc is a registered Closed Corporation under South African Law No. 2002/050421/23 SELFTOURS is an accredited member of SATSA (South African Tourism Services Association), affording you the knowledge and peace of mind that you are negotiating with a recognised and financially approved South African Tour Operator For further info click here Contact us for the many other options that we offer including the Mystical Island of Madagascar, the Spice Island of Zanzibar, the Paradise Island of Mauritius, Victoria Falls and Gorilla trekking in the Rwandan Mountains as well as tours of South Africa, all can be designed to meet your personal vacation requirements. Selftours retains the right to change the itinerary without notice where and when necessary. Subject to availability of flights, accommodation and prevailing exchange control rates at time of your booking Terms and conditions do apply. If you are unable to see the above images, please click hereThis mail is sent to you as you have in the past contacted Selftours, or entered one of our competitions, are a travel agent, or have chosen to Opt-In and receive various holiday options up dates etc. This is an honest circular to bring you news updates regarding Holiday travel. However, to change your email address or be de-listed from our holiday newsletter list - please click here - and insert the email address we must change or remove ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding MySQL-5.6 to ports
On Tue, 14 Jun 2011 09:28:04 +0200 Alex Dupre a...@freebsd.org articulated: Jerry ha scritto: I was wondering if anyone was considering adding the development branch MySQL-5.6 to the ports tree? Yes, I'm waiting for the next release. Thanks }}:-) -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Mailman + postfix -- which group have people selected?
Hi all, Before I say anything else, please _do not_ bother wxs@ on this subject -- any problems to do with ownership/groups in mailman should be sent to me-- it's my mess! I fixed mailman recently to not touch PREFIX before the install phase, which opened up a small can of worms in itself -- a fix is waiting for approval. The PR at [1] states that the value for MAIL_GROUP for using mailman with Postfix should be nobody, but [2] talks about that being wrong. Before I revert the MAIL_GID=nobody change (I have had private mail explaining that it is in fact incorrect), does anyone have any more information on which value is more correct, and why one is preferable? In short (pseudocode): .if defined(WITH_POSTFIX) MAIL_GID= nobody .endif or .if defined(WITH_POSTFIX) MAIL_GID=mailman .endif ? Comments please? (I run mailman with sendmail, and I've found it difficult to ascertain the Right Thing.) Chris [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/142000 [2] http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040293.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Mailman + postfix -- which group have people selected?
On 2011-06-14 20:43, Chris Rees wrote: Hi all, Before I say anything else, please _do not_ bother wxs@ on this subject -- any problems to do with ownership/groups in mailman should be sent to me-- it's my mess! I fixed mailman recently to not touch PREFIX before the install phase, which opened up a small can of worms in itself -- a fix is waiting for approval. The PR at [1] states that the value for MAIL_GROUP for using mailman with Postfix should be nobody, but [2] talks about that being wrong. Before I revert the MAIL_GID=nobody change (I have had private mail explaining that it is in fact incorrect), does anyone have any more information on which value is more correct, and why one is preferable? In short (pseudocode): .if defined(WITH_POSTFIX) MAIL_GID= nobody .endif or .if defined(WITH_POSTFIX) MAIL_GID=mailman .endif ? Comments please? Second one, GID=mailman The group nobody is not really secure (even it is unprivileged). Mostly the nobody group is chosen for daemons which do not write data at all. Normally you try to protect the alias databases which is not given if nobody has write access to them. From mailman-2.1.14/doc/mailman-install/postfix-integration.html When you configure Mailman, use the --with-mail-gid=mailman switch this will be the default if you configured Mailman after adding the mailman owner. Because the owner of the aliases.db file is mailman, Postfix will execute Mailman's wrapper program as uid and gid mailman. From mailman-2.1.14/doc/mailman-install/postfix-virtual.html As above with the data/aliases* files, you want to make sure that both data/virtual-mailman and data/virtual-mailman.db are user and group owned by mailman. Other Sources: http://www.seaglass.com/postfix/mailman-gid.html http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040289.html I think it is a good idea to revert the GID as soon as possible back to mailman and additional instruct postfix users to make sure the group of the alias / virtual-alias databases are set to mailman. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Mailman + postfix -- which group have people selected?
On Jun 14, 2011, at 11:43 AM, Chris Rees wrote: Before I revert the MAIL_GID=nobody change (I have had private mail explaining that it is in fact incorrect), does anyone have any more information on which value is more correct, and why one is preferable? Basically, Postfix will deliver to the owner of Mailman's alias file. So long as that is owned by mailman user, and so long as the mailman user has the mailman group as it's primary GID, then running with --with-mail-gid=mailman is correct. You'll probably find Mailman's documentation helpful: http://wiki.list.org/display/DOC/Understanding+group+mismatch+errors+-+how+mailman+implements+security http://www.seaglass.com/postfix/mailman-gid.html Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Mailman + postfix -- which group have people selected?
On 14 June 2011 21:02, Olli Hauer oha...@freebsd.org wrote: On 2011-06-14 20:43, Chris Rees wrote: Hi all, Before I say anything else, please _do not_ bother wxs@ on this subject -- any problems to do with ownership/groups in mailman should be sent to me-- it's my mess! I fixed mailman recently to not touch PREFIX before the install phase, which opened up a small can of worms in itself -- a fix is waiting for approval. The PR at [1] states that the value for MAIL_GROUP for using mailman with Postfix should be nobody, but [2] talks about that being wrong. Before I revert the MAIL_GID=nobody change (I have had private mail explaining that it is in fact incorrect), does anyone have any more information on which value is more correct, and why one is preferable? In short (pseudocode): .if defined(WITH_POSTFIX) MAIL_GID= nobody .endif or .if defined(WITH_POSTFIX) MAIL_GID=mailman .endif ? Comments please? Second one, GID=mailman The group nobody is not really secure (even it is unprivileged). Mostly the nobody group is chosen for daemons which do not write data at all. Normally you try to protect the alias databases which is not given if nobody has write access to them. From mailman-2.1.14/doc/mailman-install/postfix-integration.html When you configure Mailman, use the --with-mail-gid=mailman switch this will be the default if you configured Mailman after adding the mailman owner. Because the owner of the aliases.db file is mailman, Postfix will execute Mailman's wrapper program as uid and gid mailman. From mailman-2.1.14/doc/mailman-install/postfix-virtual.html As above with the data/aliases* files, you want to make sure that both data/virtual-mailman and data/virtual-mailman.db are user and group owned by mailman. Other Sources: http://www.seaglass.com/postfix/mailman-gid.html http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040289.html I think it is a good idea to revert the GID as soon as possible back to mailman and additional instruct postfix users to make sure the group of the alias / virtual-alias databases are set to mailman. Thank you. A patch to reverse the group change and fix the REINPLACE is in my Tinderbox -- it should be ready by tomorrow. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portinstall dependency calculation mishap
I've run into an odd problem where portinstall seems to want to double-install a package when portinstall is run from inside a bash script. The case I ran into was trying to install the postgres84-server port. In the dependencies is devel/pkg-config. When run from inside a shell script, portinstall tries to install pkg-config a second time after the postgres install is complete. If I run it outside a shell script (from my prompt) it works fine. I ran into this using my personal environment and sudo, but I've repeated it with a bare tcsh login as well as a direct login to root's account from the console, so I'm confident this isn't due to interference from something in my environment. I can work around this by installing pkg-config directly before installing postgres, but thought this was odd enough to warrant an email to the list. Repeatability is trivial on a freshly installed 8.0-RELEASE as well as on 8.2-RELEASE-p2 system with an up-to-date ports tree. cat testscript EOF #!/usr/local/bin/bash portinstall databases/postgresql84-server EOF chmod a+x testscript sudo ./testscript I've trimmed the config/cc/etc output from a log of my shell and included it below so that the order of operations can be seen. [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 22 packages found (-3 +0) (...) done] [Gathering depends for databases/postgresql84-server ... done] --- Installing 'postgresql-client-8.4.8' from a port (databases/postgresql84-client) --- Building '/usr/ports/databases/postgresql84-client' === Cleaning for libxml2-2.7.8_1 === Cleaning for pkg-config-0.25_1 === Cleaning for postgresql-client-8.4.8 === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for postgresql-client-8.4.8 === Extracting for postgresql-client-8.4.8 = SHA256 Checksum OK for postgresql/postgresql-8.4.8.tar.bz2. === Patching for postgresql-client-8.4.8 === Applying FreeBSD patches for postgresql-client-8.4.8 === postgresql-client-8.4.8 depends on executable: gmake - found === postgresql-client-8.4.8 depends on shared library: xml2.5 - not found ===Verifying install for xml2.5 in /usr/ports/textproc/libxml2 === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for libxml2-2.7.8_1 = SHA256 Checksum OK for gnome2/libxml2-2.7.8.tar.gz. === Patching for libxml2-2.7.8_1 === Applying FreeBSD patches for libxml2-2.7.8_1 === libxml2-2.7.8_1 depends on executable: gmake - found === libxml2-2.7.8_1 depends on executable: pkg-config - not found ===Verifying install for pkg-config in /usr/ports/devel/pkg-config === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for pkg-config-0.25_1 = SHA256 Checksum OK for gnome2/pkg-config-0.25.tar.gz. === Patching for pkg-config-0.25_1 === Applying FreeBSD patches for pkg-config-0.25_1 === pkg-config-0.25_1 depends on executable: gmake - found === Configuring for pkg-config-0.25_1 === Building for pkg-config-0.25_1 === Installing for pkg-config-0.25_1 === Generating temporary packing list === Checking if devel/pkg-config already installed === Compressing manual pages for pkg-config-0.25_1 === Registering installation for pkg-config-0.25_1 === Returning to build of libxml2-2.7.8_1 === libxml2-2.7.8_1 depends on shared library: iconv.3 - found === Configuring for libxml2-2.7.8_1 === Building for libxml2-2.7.8_1 === Installing for libxml2-2.7.8_1 === libxml2-2.7.8_1 depends on executable: pkg-config - found === Generating temporary packing list === Checking if textproc/libxml2 already installed === Compressing manual pages for libxml2-2.7.8_1 === Running ldconfig === Registering installation for libxml2-2.7.8_1 === Returning to build of postgresql-client-8.4.8 === postgresql-client-8.4.8 depends on shared library: intl - found === Configuring for postgresql-client-8.4.8 === Building for postgresql-client-8.4.8 === Installing for postgresql-client-8.4.8 === postgresql-client-8.4.8 depends on shared library: xml2.5 - found === postgresql-client-8.4.8 depends on shared library: intl - found === Generating temporary packing list === Checking if databases/postgresql84-client already installed === Compressing manual pages for postgresql-client-8.4.8 === Running ldconfig === Registering installation for postgresql-client-8.4.8 === Cleaning for libxml2-2.7.8_1 === Cleaning for pkg-config-0.25_1 === Cleaning for postgresql-client-8.4.8 [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 25 packages found (-0 +3) ... done] --- Installing 'pkg-config-0.25_1' from a port (devel/pkg-config) --- Building '/usr/ports/devel/pkg-config' === Cleaning for pkg-config-0.25_1 === Vulnerability check disabled, database not found === License check disabled, port
