Re: Stop in /usr/ports/multimedia/x264
Say, did you look at the port recently? :-) I have added bash as a build dependency and use it for the configure script. There are two ways I can solve this in general: 1.) add bash as a build dependency and use it for configure (I have chosen this for now, already committed) 2.) patch configure and remove/replace constructs unsupported by /bin/sh (e.g. == or [[ ]]) Cheers, mm On 22.12.2011 12:03, per...@pluto.rain.com wrote: Kevin Oberman kob6...@gmail.com wrote: I see the following errors during the configure stage: === Configuring for x264-0.119.2113 [[: not found That sure looks as if the configure script needs to be run with bash. files/patch-configure does this: -#!/bin/bash +#!/bin/sh which presumes that the script does not actually need bash extensions. However, since it does seem to need those extensions, that part of the patch should be -#!/bin/bash +#!/usr/local/bin/bash and bash needs to be added as a build dependency. (Alternatively, the configure script could be patched to not use the [[ bash builtin.) Maintainer already in Cc: list. -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: Stop in /usr/ports/multimedia/x264
On 22 December 2011 09:32, Martin Matuska m...@freebsd.org wrote: Say, did you look at the port recently? :-) I have added bash as a build dependency and use it for the configure script. There are two ways I can solve this in general: 1.) add bash as a build dependency and use it for configure (I have chosen this for now, already committed) 2.) patch configure and remove/replace constructs unsupported by /bin/sh (e.g. == or [[ ]]) 2) please, and then yell at upstream! ;) 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
Re: RUN_DEPENDS for python based port
Christer Edwards wrote on 22.12.2011 11:28: On Sun, Dec 18, 2011 at 8:22 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Looks like mailing list eats the attachment. Would you please upload it somewhere and provide us with the link. Apologies. I've uploaded the archive here: http://dl.dropbox.com/u/312414/salt-port.tar.gz Sorry for delay. Please review this patch: http://people.freebsd.org/~rm/salt.diff.txt it fixes: - fetch (FETCH_ARGS added, that i noted erlier) - build (you mistyped py-Jinja2 dependency) - python version changed to 2.6-2.7 - whitespace issue (spotted by portlint) - man-pages install - configuration files install - missing files in pkg-plist This port is now builds/installs cleanly, but i haven't checked runtime after that. -- 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: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/12/2011 10:06, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description: The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream expiration date: 2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=gtkfind This was supposed to have been resuscitated. Is its continued inclusion here fallout from the svn/cvs issue, or is there another problem? Don't worry, it's still definitely undeprecated :) Mark, has the tree got out of date again? Chris -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO8wB6AAoJELCEktHh68rEd6EH/je2T2kBAj2M7ZtMnfb1pA1g s0uhGWUk8YxE0UQuqxty9S0ZRQ/+tOzHS+7PDfvW/MMxVpv6c3nlin+BdlqTrMWV baIjvSr6KBKnSHb6j/LJflAfO9vZVNO5TUNk8dX14qdyon9o1Po7Orf/Hj1gt7by /HgQWuVomSYluQa1i/uIg2I+/iYiPAvV5cNTruJt1Fj5VfEdDPRXVeCUob85HCWJ T6HW67zZnxNlE4oAYrznwGuBle8IsVRbbwwVvnjxCv3/uB8yVIwtW44zdo+Mqc3B GRPwHfLmwhPZ8BaCNvuStYNlqwiiRoAOSgGT3fxtslAe9wV3vLr0gqqo4NQp10Y= =VKNz -END PGP SIGNATURE- ___ 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: automoc4 deadlocks in parallel runs
On Thu, 22 Dec 2011, Dmitry Morozovsky wrote: re: http://permalink.gmane.org/gmane.os.freebsd.stable/75521 Any progress with this? My tinderbox can't build any automoc4-related ports for few weeks... Thanks in advance. Could you test the following patch http://people.freebsd.org/~cognet/qprocess_unix.cpp.diff for devel/qt4- corelib? Yesss! At least kdelibs4 has been built successfully, while before it almost always got stuck at 0-2% cmake completeness. Two tinderbuilds for x11/kde4 -j4 each are still run; I'll report with final results tomorrow. I can confirm both kde4 tinderbuilds have been finished successfully. (CC:d ports@ fot tracking purposes) What could we do to make this committed? Thank you very much! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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
freebsd 9 crashes
freebsd 9-prerel
amd64
ejabberd port, 2.1.9
runs for one or more hours then crashes leaving beam.smp.core, which i
am not sure how to decode as i can not find beam.smp
i commented out pubsub due to rumors of memory leak
clue bat, please
randy
---
# cat /usr/local/etc/ejabberd/ejabberd.cfg
% 2009.09.28
% Host name:
{hosts, [ jabber.rg.net ] }.
% Default language for server messages
{language, en}.
% Authentication method. If you want to use internal user base, then use
% this line:
{auth_method, internal}.
% Users that have admin access. Add line like one of the following after you
% are successfully registered on server to get admin access:
{acl, admin, {user, randy,jabber.rg.net}}.
{acl, web_admin, {user, randy,jabber.rg.net}}.
%{acl, admin, {user, ra...@jabber.rg.net}}.
{acl, web_admin, {user, ra...@jabber.rg.net}}.
% Local users:
{acl, local, {user_regexp, }}.
% bad users
{acl, blocked, {user, bad}}.
% Only admins can use configuration interface:
{access, configure, [{allow, admin}]}.
% Every username can be registered via in-band registration:
{access, register, [ {allow, all} ] }.
% After successful registration user will get message with following subject
% and body:
{welcome_message,
{Welcome!,
Welcome to Jabber Service at jabber.rg.net.
For information about Jabber visit http://jabber.org}}.
% Replace them with 'none' if you don't want to send such message:
%{welcome_message, none}.
% List of people who will get notifications about registered users
{registration_watchers, [ra...@jabber.rg.net]}.
% Only admins can send announcement messages:
{access, announce, [{allow, admin}]}.
% Only non-blocked users can use c2s connections:
{access, c2s, [{deny, blocked}, {allow, all}] }.
% Set shaper with name normal to limit traffic speed to 50kB/s
{shaper, normal, {maxrate, 5}}.
% For all S2S connections used normal shaper
{access, s2s_shaper, [{normal, all}]}.
% All users are allowed to use MUC service:
{access, muc, [{allow, all}]}.
% Admins of this server are also admins of MUC service:
{access, muc_admin, [{allow, admin}]}.
{ listen,
[ {5222, ejabberd_c2s, [ { access, c2s },
starttls,
{ certfile, /usr/local/etc/key.pem } ]
},
{5223, ejabberd_c2s, [ { access, c2s },
tls,
{ certfile, /usr/local/etc/key.pem } ]
},
{15222, ejabberd_c2s,[ inet6,
{ access, c2s },
starttls,
{ certfile, /usr/local/etc/key.pem } ]
},
{15223, ejabberd_c2s,[ inet6,
{ access, c2s },
tls,
{ certfile, /usr/local/etc/key.pem } ]
},
{5269, ejabberd_s2s_in, [ {shaper, s2s_shaper}
]
},
{15269, ejabberd_s2s_in, [ inet6,
{shaper, s2s_shaper}
]
},
{5280, ejabberd_http,[ http_poll, web_admin,
tls, { certfile, /usr/local/etc/key.pem }
]
%% },
%% {5347, ejabberd_service, [ { host, aim.rg.net,
%%[ { password, 87ybkjhkiui7 } ]
%% } ]
}
]
}.
% If SRV lookup fails, then port 5269 is used to communicate with remote
{outgoing_s2s_port, 5269}.
{modules,
[{mod_register, [ {access, register} ] },
{mod_announce, [ {allow, admin} ] },
{mod_roster,[] },
{mod_privacy, [] },
{mod_configure, [] },
{mod_configure2,[]},
{mod_disco, [] },
{mod_stats, [] },
{mod_vcard, [] },
{mod_offline, [] },
{mod_private, [] },
{mod_muc, [ {host, conf.rg.net},
{access, muc},
{access_create, muc},
{access_admin, muc_admin}
] },
%%{mod_pubsub,[] },
{mod_time, [ {iqdisc, no_queue} ] },
{mod_last, [] },
{mod_version, [] }
]
}.
___
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: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 1:32 AM, Martin Matuska m...@freebsd.org wrote: Say, did you look at the port recently? :-) I have added bash as a build dependency and use it for the configure script. There are two ways I can solve this in general: 1.) add bash as a build dependency and use it for configure (I have chosen this for now, already committed) 2.) patch configure and remove/replace constructs unsupported by /bin/sh (e.g. == or [[ ]]) Thanks for the quick fix, but I am still baffled as to why it built correctly on two of my three systems where it's installed. All three complained about the '[[' type constructs, but only one spit out the x264_CSP|all error and al of the other completed the build. It is possible that the build was not quite right as a result of the errors, but why did only one fail completely? The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Again, thanks again for the quick fix. I tend to prefer #2 if there is no real reason for bash, but almost all systems used for multimedia work already have bash installed, so it's not a big deal. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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: Stop in /usr/ports/multimedia/x264
Kevin Oberman wrote on 22.12.2011 20:38: The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. -- 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: Stop in /usr/ports/multimedia/x264
On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kevin Oberman wrote on 22.12.2011 20:38: The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. True, since 9 sh supports == -- however I might label this compatibility shims, rather than 'improvements'... 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
Re: Stop in /usr/ports/multimedia/x264
Chris Rees wrote on 22.12.2011 22:12: On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kevin Oberman wrote on 22.12.2011 20:38: The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. True, since 9 sh supports == -- however I might label this compatibility shims, rather than 'improvements'... Chris I'm talking about overall /bin/sh work, not only about compatibility with some `non-true' shells. I know many things was done and tests coverage is terrific. So may we imply dependency on shells/bash and specific configure patches only if OSVERSION 90? -- 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: Stop in /usr/ports/multimedia/x264
On 22 Dec 2011 18:20, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Chris Rees wrote on 22.12.2011 22:12: On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kevin Oberman wrote on 22.12.2011 20:38: The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. True, since 9 sh supports == -- however I might label this compatibility shims, rather than 'improvements'... Chris I'm talking about overall /bin/sh work, not only about compatibility with some `non-true' shells. I know many things was done and tests coverage is terrific. So may we imply dependency on shells/bash and specific configure patches only if OSVERSION 90? Trouble is with these problems is that they can hide, and don't always result in outright failure (i've experienced this with musicpd and Clamav). The scripts need a proper audit before being declared sh-safe. 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
Re: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 2:43 AM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Sorry for delay. Please review this patch: http://people.freebsd.org/~rm/salt.diff.txt it fixes: - fetch (FETCH_ARGS added, that i noted erlier) - build (you mistyped py-Jinja2 dependency) - python version changed to 2.6-2.7 - whitespace issue (spotted by portlint) - man-pages install - configuration files install - missing files in pkg-plist Wow. Thank you for those fixes! Everything seems to build correctly for me now, but I'm wondering if I didn't apply the setup.py patch properly because I'm still not getting the config files. Do you think you could tell me how setup.py patch is supposed to be used from files/? Thanks ___ 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: RUN_DEPENDS for python based port
Christer Edwards wrote on 22.12.2011 23:54: On Thu, Dec 22, 2011 at 2:43 AM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Sorry for delay. Please review this patch: http://people.freebsd.org/~rm/salt.diff.txt it fixes: - fetch (FETCH_ARGS added, that i noted erlier) - build (you mistyped py-Jinja2 dependency) - python version changed to 2.6-2.7 - whitespace issue (spotted by portlint) - man-pages install - configuration files install - missing files in pkg-plist Wow. Thank you for those fixes! Everything seems to build correctly for me now, but I'm wondering if I didn't apply the setup.py patch properly because I'm still not getting the config files. Do you think you could tell me how setup.py patch is supposed to be used from files/? Thanks Here is updated tarball (couple of lines in pkg-plist fixed dealing with config files): http://people.freebsd.org/~rm/salt.tbz Config files (master and minion) installed into /usr/local/etc/salt/ by default: [rm@smeshariki3 /tmp] ls -l /usr/local/etc/salt/ total 16 -rw-r--r-- 1 root wheel 6223 28 ноя 02:14 master -rw-r--r-- 1 root wheel 4242 25 окт 08:48 minion Btw, i'd prefer to patch setup.py once again to install them with '.sample' postfix. User will need to copy them into just `master' and `minion' to make it work. This will guarantee that user will not lost their configuration while upgrading salt to new version from ports. You should change this block in setup.py: data_files=[(os.path.join(etc_path, 'salt'), ['conf/master', 'conf/minion', ]), Just add '.sample' postfix to this file names. And similar change in pkg-plist: %%ETCDIR%%/master.sample %%ETCDIR%%/minion.sample instead of %%ETCDIR%%/master %%ETCDIR%%/minion More about patching here: http://www.freebsd.org/doc/en/books/porters-handbook/book.html#SLOW-PATCH -- 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: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 1:31 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Btw, i'd prefer to patch setup.py once again to install them with '.sample' postfix. User will need to copy them into just `master' and `minion' to make it work. This will guarantee that user will not lost their configuration while upgrading salt to new version from ports. I've updated this in the patch-setup.py and the pkg-plist as suggested. This is starting to really come together, thank you! At this point I believe all I have left is to write init scripts for the minion and master and it should be ready to go. That reminds me, what method should I use to include a short message on getting things running post installation? ie; cp the .sample files into place and update rc.conf, etc. Thanks again for all the help! Christer ___ 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: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 10:57 AM, Chris Rees utis...@gmail.com wrote: On 22 Dec 2011 18:20, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Chris Rees wrote on 22.12.2011 22:12: On 22 Dec 2011 16:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kevin Oberman wrote on 22.12.2011 20:38: The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Yes, all is worked just fine (before the bash fix commit) there on 10.0-CURRENT i386. I saw that configure warnings too, but it still was built successfully. May be bash only needed on some older FreeBSD versions like 8.2, that didn't had all that improvements for /bin/sh, that were merged in 9 and 10, so maybe it is the reason why it builded fine on this systems w/o any additional fixes. True, since 9 sh supports == -- however I might label this compatibility shims, rather than 'improvements'... Chris I'm talking about overall /bin/sh work, not only about compatibility with some `non-true' shells. I know many things was done and tests coverage is terrific. So may we imply dependency on shells/bash and specific configure patches only if OSVERSION 90? Trouble is with these problems is that they can hide, and don't always result in outright failure (i've experienced this with musicpd and Clamav). The scripts need a proper audit before being declared sh-safe. Chris Yes! Even with versions where it works, I get a number of errors reported during configure. So, while it built, I am not sure that it built right. I may be lacking optimizations or picking up bugs. Either the script should be fixed to be fully compatible with sh or bash should be used. I don't mind if it is dependent on bash for pre-9.0, but, again, I doubt many systems running multimedia apps lack the bash port, already, so requiring bash is probably going to impact few and the impact is pretty minor! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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: RUN_DEPENDS for python based port
On Thu, Dec 22, 2011 at 1:52 PM, Christer Edwards christer.edwa...@gmail.com wrote: At this point I believe all I have left is to write init scripts for the minion and master and it should be ready to go. That reminds me, what method should I use to include a short message on getting things running post installation? ie; cp the .sample files into place and update rc.conf, etc. I must have horrible luck or something, but I've put together rc scripts and they don't work. This port sure is giving me a hard time! Here is a link to the updated archive with the .sample suggestions applied as well as the rc scripts. Can anyone see what is wrong with them? I simply get complains that it isn't toggled to YES in the rc.conf, but it is.. http://dl.dropbox.com/u/312414/salt-port-2011-12-22.tar.gz Thanks again ___ 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
salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 16:32, Christer Edwards wrote:
I must have horrible luck or something, but I've put together rc
scripts and they don't work. This port sure is giving me a hard time!
Here is a link to the updated archive with the .sample suggestions
applied as well as the rc scripts. Can anyone see what is wrong with
them? I simply get complains that it isn't toggled to YES in the
rc.conf, but it is..
Can you paste the actual error that you're getting, and the output of
'grep salt /etc/rc.conf /etc/rc.conf.local' please?
I reviewed your scripts, and there is nothing that should cause the
error you're describing. I even tried with and without
salt_master_enable in rc.conf and got the expected results for both.
There are some style problems and one real bug that are repeated for all
3 scripts. I attached a fixed version of one of them, hopefully that
will help you see what's needed to fix the other 2. Also, please review
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html,
especially the pre-commit checklist.
hth,
Doug
--
[^L]
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
#!/bin/sh
# $FreeBSD$
#
# Salt Master startup script
#
# PROVIDE: salt-master
# REQUIRE: LOGIN
# KEYWORD: shutdown
#
# Add the following to /etc/rc.conf[.local] to enable this service
#
# salt_master_enable=YES
. /etc/rc.subr
name=salt-master
rcvar=salt_master_enable
load_rc_config ${name}
: ${salt_master_enable:=NO}
command=%%PREFIX%%/bin/${name}
pidfile=/var/run/${name}.pid
required_files=%%PREFIX%%/etc/salt/master
command_args=-c $required_files -d
run_rc_command $1
___
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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton do...@freebsd.org wrote: There are some style problems and one real bug that are repeated for all 3 scripts. I attached a fixed version of one of them, hopefully that will help you see what's needed to fix the other 2. Also, please review http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. http://pastebin.com/raw.php?i=2wGBk0PY thanks ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/22/11 8:34 PM, Christer Edwards wrote: On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton do...@freebsd.org wrote: There are some style problems and one real bug that are repeated for all 3 scripts. I attached a fixed version of one of them, hopefully that will help you see what's needed to fix the other 2. Also, please review http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. http://pastebin.com/raw.php?i=2wGBk0PY thanks Hi Christer, The salt-master script is interpreted by Python, so I believe you'll need the following in your rc.d script: command_interpreter=%%PYTHON_CMD%% and the proper SUB_LIST setting in the Makefile. Check the py-fail2ban port for some pointers on that. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7z4O8ACgkQ0sRouByUApBavgCfTCmlEwuPyOvJBLjK2OS99uwd sNUAnjjKqPeiNIKhIwrmb/vSfu9JDtjS =KVha -END PGP SIGNATURE- ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 17:34, Christer Edwards wrote: On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton do...@freebsd.org wrote: There are some style problems and one real bug that are repeated for all 3 scripts. I attached a fixed version of one of them, hopefully that will help you see what's needed to fix the other 2. Also, please review http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. Try doing s/-/_/ for all the $name variables. I think that's what's causing your problem. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 18:01, Greg Larkin wrote: On 12/22/11 8:34 PM, Christer Edwards wrote: On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton do...@freebsd.org wrote: There are some style problems and one real bug that are repeated for all 3 scripts. I attached a fixed version of one of them, hopefully that will help you see what's needed to fix the other 2. Also, please review http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. http://pastebin.com/raw.php?i=2wGBk0PY thanks Hi Christer, The salt-master script is interpreted by Python, so I believe you'll need the following in your rc.d script: command_interpreter=%%PYTHON_CMD%% and the proper SUB_LIST setting in the Makefile. Check the py-fail2ban port for some pointers on that. Yeah, that should help with stopping the service, and is one of the reasons why I suggested reviewing the PH page for rc.d scripts. :) I'm not sure it's what is causing the startup problem though. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/22/11 9:01 PM, Greg Larkin wrote: On 12/22/11 8:34 PM, Christer Edwards wrote: On Thu, Dec 22, 2011 at 5:45 PM, Doug Barton do...@freebsd.org wrote: There are some style problems and one real bug that are repeated for all 3 scripts. I attached a fixed version of one of them, hopefully that will help you see what's needed to fix the other 2. Also, please review http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html, especially the pre-commit checklist. I made the changes you suggested and tried a fresh build of the port inside of a jail. Below is a pastebin of trying to start the service(s) just after installation. http://pastebin.com/raw.php?i=2wGBk0PY thanks Hi Christer, The salt-master script is interpreted by Python, so I believe you'll need the following in your rc.d script: command_interpreter=%%PYTHON_CMD%% and the proper SUB_LIST setting in the Makefile. Check the py-fail2ban port for some pointers on that. Hope that helps, Greg Also, I forgot to mention that when I'm faced with similar rc.d problems, I invoke the script with sh -x like so: sh -x /usr/local/etc/rc.d/viewvc start That prints all of the shell variable debug information, echoes commands, etc. I would be interested in seeing that output if you can post it to pastebin. I'm not sure my previous suggestion will help anyway, and it looks like your $command variable is trashed somewhere while the script executes. Regards, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7z4dEACgkQ0sRouByUApDzfgCgkoTH5sNuPr+jEdbp9rplFD2b BoAAoJbTTQBZi0oL8URD7C71/7hsKVgU =Uu2Z -END PGP SIGNATURE- ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 7:01 PM, Doug Barton do...@freebsd.org wrote: Try doing s/-/_/ for all the $name variables. I think that's what's causing your problem. I did a little more testing (and I added the Makefile and .in file suggestions). I can now get it to run consistently if I change $name to use all underscores, and also update $command to 'salt-master' instead of $name. Definitely something funny about having dashes in the name I guess. Also, one last thing.. anytime I try to stop the newly started services they each complain about 'salt_master not running? (check /var/run/salt_master.pid).' Do I need to create the pid in the rc script, or in the Makefile? Very, very close now. Thanks again for all the help guys. ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 18:28, Christer Edwards wrote: On Thu, Dec 22, 2011 at 7:01 PM, Doug Barton do...@freebsd.org wrote: Try doing s/-/_/ for all the $name variables. I think that's what's causing your problem. I did a little more testing (and I added the Makefile and .in file suggestions). I can now get it to run consistently if I change $name to use all underscores, and also update $command to 'salt-master' instead of $name. Definitely something funny about having dashes in the name I guess. Right. Also, one last thing.. anytime I try to stop the newly started services they each complain about 'salt_master not running? (check /var/run/salt_master.pid).' Do I need to create the pid in the rc script, or in the Makefile? You need to pay attention to what Greg told you, and read the Handbook page that I sent. :) Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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
FreeBSD Port: freehdl-0.0.7
RE: freehdl and qucs running digital simulation , 2 inputs to an AND gate , gives error cd: can't cd to vhdl libtool: link: cannot determine absolute directory name of `vhdl' This appears to be a problem in the freehdl package . Can you tell me how to fix it ? Thank you, Barry Tigner ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Thu, Dec 22, 2011 at 8:12 PM, Doug Barton do...@freebsd.org wrote: You need to pay attention to what Greg told you, and read the Handbook page that I sent. :) OK. I give. I've read that Handbook page a number of times and nothing is jumping out at me. I've been tinkering and testing all evening and I'm just not getting it to work. I'd really like to know what I'm missing. I feel like it's going to be really obvious once someone points it out, but until then.. I'm just not seeing it. The archive below is what I currently have.. http://dl.dropbox.com/u/312414/salt-port-2011-12-23.tar.gz Christer ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 23:05, Christer Edwards wrote: On Thu, Dec 22, 2011 at 8:12 PM, Doug Barton do...@freebsd.org wrote: You need to pay attention to what Greg told you, and read the Handbook page that I sent. :) OK. I give. I've read that Handbook page a number of times and nothing is jumping out at me. I've been tinkering and testing all evening and I'm just not getting it to work. I'd really like to know what I'm missing. I feel like it's going to be really obvious once someone points it out, but until then.. I'm just not seeing it. Did you read the pre-commit checklist? Particularly item 7? -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:11 AM, Doug Barton do...@freebsd.org wrote: Did you read the pre-commit checklist? Particularly item 7? If the script uses an interpreted language like perl, python, or ruby, make certain that command_interpreter is set appropriately. Each rc script includes: 'command_interpreter=%%PYTHON_CMD%%' as suggested earlier. I looked at another port (security/denyhosts) and noticed it used %%PYTHON%% vs %%PYTHON_CMD%%, but either way after installation it expands properly to /usr/local/bin/python2.7 as I would expect.. Again, the error I'm finding is: [root@salt /usr/local/etc/rc.d]# ./salt_master start Starting salt_master. [root@salt /usr/local/etc/rc.d]# ./salt_master stop salt_master not running? (check /var/run/salt_master.pid). ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 23:21, Christer Edwards wrote: On Fri, Dec 23, 2011 at 12:11 AM, Doug Barton do...@freebsd.org wrote: Did you read the pre-commit checklist? Particularly item 7? If the script uses an interpreted language like perl, python, or ruby, make certain that command_interpreter is set appropriately. Each rc script includes: 'command_interpreter=%%PYTHON_CMD%%' as suggested earlier. I looked at another port (security/denyhosts) and noticed it used %%PYTHON%% vs %%PYTHON_CMD%%, but either way after installation it expands properly to /usr/local/bin/python2.7 as I would expect.. excellent. Again, the error I'm finding is: [root@salt /usr/local/etc/rc.d]# ./salt_master start Starting salt_master. [root@salt /usr/local/etc/rc.d]# ./salt_master stop salt_master not running? (check /var/run/salt_master.pid). So now do 'ps axww | grep salt' and confirm that it's really running with python2.7, as opposed to something different. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:32 AM, Doug Barton do...@freebsd.org wrote: So now do 'ps axww | grep salt' and confirm that it's really running with python2.7, as opposed to something different. Indeed it is running with python2.7 Here is some ps output before and after starting the rc script: http://pastebin.com/raw.php?i=d86Mgq3N ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 23:40, Christer Edwards wrote: On Fri, Dec 23, 2011 at 12:32 AM, Doug Barton do...@freebsd.org wrote: So now do 'ps axww | grep salt' and confirm that it's really running with python2.7, as opposed to something different. Indeed it is running with python2.7 Ok, does the pid file exist? Does it have the correct information? -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:43 AM, Doug Barton do...@freebsd.org wrote: On 12/22/2011 23:40, Christer Edwards wrote: On Fri, Dec 23, 2011 at 12:32 AM, Doug Barton do...@freebsd.org wrote: So now do 'ps axww | grep salt' and confirm that it's really running with python2.7, as opposed to something different. Indeed it is running with python2.7 Ok, does the pid file exist? Does it have the correct information? The pid file does not seem to get created. See this output.. [root@salt /usr/local/etc/rc.d]# ls -hal /var/run/salt* ls: /var/run/salt*: No such file or directory [root@salt /usr/local/etc/rc.d]# ./salt_master start Starting salt_master. [root@salt /usr/local/etc/rc.d]# ls -hal /var/run/salt* ls: /var/run/salt*: No such file or directory [root@salt /usr/local/etc/rc.d]# ps axww | grep salt 13130 ?? SJ 0:00.10 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13131 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13132 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13133 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13134 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13135 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13136 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d 13137 ?? SJ 0:00.01 /usr/local/bin/python2.7 /usr/local/bin/salt-master -c /usr/local/etc/salt/master -d ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On 12/22/2011 23:47, Christer Edwards wrote: The pid file does not seem to get created. Ok, so fix it. :) Setting 'pidfile' in the rc.d script is only useful if the service creates a pid file. It's not magic. Given that the thing seems to create a lot of instances of itself, and one pid may not be enough, you might want to try commenting out the pidfile in the script and see if that works. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: salt rc.d scripts (Was: RUN_DEPENDS for python based port)
On Fri, Dec 23, 2011 at 12:51 AM, Doug Barton do...@freebsd.org wrote: On 12/22/2011 23:47, Christer Edwards wrote: The pid file does not seem to get created. Ok, so fix it. :) Setting 'pidfile' in the rc.d script is only useful if the service creates a pid file. It's not magic. Given that the thing seems to create a lot of instances of itself, and one pid may not be enough, you might want to try commenting out the pidfile in the script and see if that works. /facepalm - that works. Now that I feel adequately defeated by something so simple, I'm going to bed :) Thanks again for all the help. ___ 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
