tinderbox start issue/error
while testing a 'pre_start()' option for tinderbox, I came across an issue.
(I backed out my patches to check)
tinderbox can be started, over, and over, and over, with no errors
warning that it is already running.
is this the expected behavior? (and you don't need root!)
%service tinderbox status 85793 85794
%service tinderbox start
%sudo service tinderbox start
%sudo service tinderbox status
tinderd is running as pid 85793 85794 85893 85894 78931 78932.
%sudo service tinderbox start
%sudo service tinderbox status
tinderd is running as pid 85793 85794 85893 85894 86001 86002 78931 78932.
%pwd
/usr/local/etc/rc.d
%cd /etc/rc.conf.d
%sudo rm tinderbox new
%service tinderbox start
%service tinderbox status
tinderd is running as pid 85793 85794 85893 85894 86001 86002 86169
86170 78931 78932.
grep tinder /etc/rc.conf
tinderd_enable="YES"
tinderd_directory=/disk1/tinderbox/scripts
tinderd_instances=2
is it because of the tinderd_instances=2? (note, each 'start' started two)
noop, (but, deleting that line lets me start another one)
service tinderbox status
tinderd is running as pid 85793 85794 85893 85894 86001 86002 86169
86170 78931 78932.
%service tinderbox start
%service tinderbox status
tinderd is running as pid 85793 85794 85893 85894 86001 86002 86169
86170 87716 78931 78932.
is this the expected behavior?
non root can start it?
you can start it, over and over and over?
is this a solution for both?
--- /tmp/tinderbox2012-01-12 10:32:24.0 -0500
+++ ./tinderbox2012-01-13 22:42:44.0 -0500
@@ -41,7 +41,19 @@
fi
start_cmd="${name}_start"
-
+start_precmd="${name}_prestart"
+tinderd_prestart()
+{
+if pgrep -f ${command} >/dev/null
+then
+err 1 ${command} already running
+fi
+ID=`id -u`
+if [ ${ID} -ne 0 ]
+then
+err 1 must be run as root
+fi
+}
tinderd_start()
{
for i in `jot - 1 ${tinderd_instances}`; do
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
___
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"
OT: Tinderbox and kernel building
I know this is not ports related, but the tool is :) So thought this would be the best place for an answer. Anyway, one can use Tinderbox to build port packages for users; but can it be used to build kernel binaries too? Or maybe I'm just off my rocker... Cheers ___ 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: [Update] Gdal 1.8.1 -> 1.9.0
"coder.tuxfamily" writes:
> There is a new version of Gdal (graphics/gdal) 1.9.0.
> Here the diff, seems works but don't have time to make all tests.
[...]
> @@ -17,7 +16,7 @@
> COMMENT= A translator library for geospatial data formats
>
> CONFIGURE_ARGS= --datadir=${DATADIR} --with-libz=/usr
> -CONFIGURE_ENV= LDFLAGS="${LDFLAGS}"
> +CONFIGURE_ENV= LDFLAGS+="${LDFLAGS}"
> GNU_CONFIGURE= yes
> LDFLAGS+=-L${LOCALBASE}
> MAKEFILE=GNUmakefile
Passing LDFLAGS seems redundant since ports/157936. The line was added
just a day before the sweeping removal.
___
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: [Update] Gdal 1.8.1 -> 1.9.0
coder.tuxfamily wrote on 13.01.2012 23:02: Hi, There is a new version of Gdal (graphics/gdal) 1.9.0. Here the diff, seems works but don't have time to make all tests. best regards 1. the diff is inverted. 2. this port has it's maintainer 3. please submit corrected patch as GNATS PR -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: multimedia/zoneminder: rc script runs mysql commands?
On Fri, 13 Jan 2012 03:20:13 -0600, Alex Dupre wrote: Boris Samorodov ha scritto: Actually this should not happen. mysql rc script has a poststart directive to wait until the daemon is up and running. Last time I used the port (zoneminder) a year ago. It was the case. Has something changed in a year? MySQL rc script was patched 3 years ago. Sounds like it's safe to remove this from zoneminder then. ___ 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"
devel/valgrind fails to build on 9.0
Hi there, Since my update to 9.0 I tried to update valgrind but it fails to build: cc -B/usr/lib32 -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -fpic -O -g -fno-omit-frame-pointer -fno-strict-aliasing -Wno-long-long -O2 -pipe -fno-strict-aliasing -Wno-pointer-sign -fno-stack-protector -nodefaultlibs -shared -Wl,-z,interpose,-z,initfirst -B/usr/lib32 -m32 -o vgpreload_core-x86-freebsd.so vgpreload_core_x86_freebsd_so-vg_preloaded.o /usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crti.o' is incompatible with i386 output /usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crtbeginS.o' is incompatible with i386 output /usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crtendS.o' is incompatible with i386 output /usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/crtn.o' is incompatible with i386 output cc: Internal error: Segmentation fault: 11 (program ld) Please submit a full bug report. See http://gcc.gnu.org/bugs.html> for instructions. gmake[3]: *** [vgpreload_core-x86-freebsd.so] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2/coregrind' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/valgrind/work/valgrind-freebsd-3.6.1-2' gmake: *** [all] Error 2 *** Error code 1 I'm guessing if my WITHOUT_LIB32 may cause this error. This is on my amd64 machine. Cheers, -- Demelier David ___ 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: mysql-server-5.0.92
I forgot to add that I'm willing to help, I already have 7.1.13 and 7.2.2 of mysql cluster working and I'd be glad to help you. I've already posted to the forms. I'm Meroverance http://forums.freebsd.org/showthread.php?p=161103 From: Shaddox, William Sent: Friday, January 06, 2012 4:24 PM To: 'a...@freebsd.org' Cc: 'po...@freebsd.org' Subject: FreeBSD Port: mysql-server-5.0.92 I'm doing testing with running MySQL-cluster versions 7.1.13 and 7.2.2 on FreeBSD and I was wondering if you had any plans for porting MySQL-cluster to FreeBSD? If you do, what might the time frame be for a MySQL-cluster port? I know 7.2.2 is beta, so I wouldn't want that to be ported, I just wanted to see the differences with the changes they added from the 5.1 to 5.5 version change they did. William M. Shaddox ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/13/12 07:51, Da Rock wrote: On 01/13/12 04:19, Chris Rees wrote: On 12 January 2012 12:26, Da Rock wrote: On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a "WARN: no CVS directories. Use -N to check a new port." Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with "looks fine". I'll upload a new .shar to my URI now. Hm, for a new port, you should use portlint -A; portlint -C is for existing ports. portlint -A searches for stupid things like a work/ directory still existing too. portlint -A: looks fine. I'll put it in later today, I think. I've implemented some more cutbacks to create a leaner port thanks to Chris' helpful comments in another thread (unassociated shell command), and I've uploaded the new shar for review (again on my URI) if anyone would care to check it out and comment. Otherwise I'll submit it tomorrow. Once submitted do the committers offer any advice on improvements? ___ 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: unassociated shell command
On 01/13/12 17:20, Chris Rees wrote: On 12 January 2012 22:38, Da Rock wrote: On 01/13/12 07:30, Chris Rees wrote: Also, no, you shouldn't (can't) set Make variables inside a target, as covered before. However... instead of .if defined(NOPORTDOCS) PLIST_SUB etc etc stuff, just remove all the PORTDOCS lines from pkg-plist, and use the magic variable PORTDOCS: PORTDOCS= * :) I must be a little slow this morning... I don't get it. How does that work? I would like to point out also that the docs are 30/70 nss and pam related respectively. So if I install without pam then the pam docs are not installed. > From Porter's Handbook: If a directory is listed in PORTDOCS or matched by a glob pattern from this variable, the entire subtree of contained files and directories will be registered in the final packing list. Basically, PORTDOCS=* is the same as including find `make -V DOCSDIR` in the pkg-plist, without the plist bloat and complication. http://www.freebsd.org/doc/en/books/porters-handbook/book.html#INSTALL-DOCUMENTATION Thats fantastic! Thanks for pointing it out (again, might have saved some headaches earlier...); I read that handbook front to back, but its not always obvious that 2 and 2 go together unless someone points it out :) Ports looking better than ever now- very lean. ___ 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: patch net/samba4-devel: fix build on 8 amd64
On 2012/01/13 00:37, Gennady wrote: With this patches port samba4-devel compile.Checked up on FreeBSD 8.2, 8-stable amd64. Committed, thanks! -- Pav Lucistnik ___ 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: multimedia/zoneminder: rc script runs mysql commands?
Boris Samorodov ha scritto: Actually this should not happen. mysql rc script has a poststart directive to wait until the daemon is up and running. Last time I used the port (zoneminder) a year ago. It was the case. Has something changed in a year? MySQL rc script was patched 3 years ago. -- 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"
