Re: 4.7 changes to /bin/sh?
The line it bitched about was something like: [ -x ${PREFIX}/sbin/thttpd_wrapper ] ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' I presume it was complaining about running a command in the background and then trying to use the operator to run the following command. Your diagnosis is correct. This change is even mentioned in 4.7 release notes (which I read *after* posting similar message to this list a few weeks agog). I don't know about thttpd_wrapper, but with my scripts (mysql_server.sh and pwcheck.sh) I could just remove the single and the scripts started to work OK. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * One can never know for sure what a deserted area looks like. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Wednesday, November 27, 2002, at 01:56 AM, Kris Kennaway wrote: I already told you in the section of my mail you deleted. Kris mime-attachment No, it's the construction, which is illegal and should never have been allowed. Update to the latest version of the port and submit a PR if the bug persists. Kris I guess I didn't understand your answer (above) to the question What changed?. If the port was broken from the get go, I think it was odd that I only noticed that the database on my server wasn't starting after my upgrade to 4.7 (which of course very well may have been the case :) Just my 2 pesos Brian -- Brian Jackson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Wednesday, November 27, 2002, at 09:23 AM, Toomas Aas wrote: Your diagnosis is correct. This change is even mentioned in 4.7 release notes (which I read *after* posting similar message to this list a few weeks agog). Thanks very much for the pointer to the release notes!!! That answered my question. Brian -- Brian Jackson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
At 04:23 PM 11.27.2002 +0200, Toomas Aas wrote: The line it bitched about was something like: [ -x ${PREFIX}/sbin/thttpd_wrapper ] ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' I presume it was complaining about running a command in the background and then trying to use the operator to run the following command. Your diagnosis is correct. This change is even mentioned in 4.7 release notes (which I read *after* posting similar message to this list a few weeks agog). I don't know about thttpd_wrapper, but with my scripts (mysql_server.sh and pwcheck.sh) I could just remove the single and the scripts started to work OK. -- h I removed the and left the single and that worked fine too. Guess either one is right if it works Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
# [EMAIL PROTECTED] / 2002-11-27 09:31:33 -0500: On Wednesday, November 27, 2002, at 01:56 AM, Kris Kennaway wrote: I already told you in the section of my mail you deleted. No, it's the construction, which is illegal and should never have been allowed. Update to the latest version of the port and submit a PR if the bug persists. Kris please, quote others correctly. this looks like you wrote this message with someone named Kris. I guess I didn't understand your answer (above) to the question What changed?. If the port was broken from the get go, I think it was odd that I only noticed that the database on my server wasn't starting after my upgrade to 4.7 (which of course very well may have been the case :) you guess right: you don't understand his answer. :) he says: /bin/sh was broken up to 4.7 in that it allowed . the port that broke for you abused this bug; you can get rid of it by updating your ports tree. doing so will get you an updated version of the port in which the $PREFIX/etc/rc.d script was fixed to not rely on that buggy behavior. Kris, please correct me if I read that wrong. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Wed, Nov 27, 2002 at 09:31:33AM -0500, Brian Jackson wrote: On Wednesday, November 27, 2002, at 01:56 AM, Kris Kennaway wrote: I already told you in the section of my mail you deleted. Kris mime-attachment No, it's the construction, which is illegal and should never have been allowed. Update to the latest version of the port and submit a PR if the bug persists. Kris I guess I didn't understand your answer (above) to the question What changed?. If the port was broken from the get go, I think it was odd that I only noticed that the database on my server wasn't starting after my upgrade to 4.7 (which of course very well may have been the case :) /bin/sh no longer allows the illegal construct (see the release notes). Kris msg10420/pgp0.pgp Description: PGP signature
4.7 changes to /bin/sh?
Hi: I installed the port for thttpd, and when I upgraded to 4.7, it broke my rc.d script, complaining about an unexpected ''. The line it bitched about was something like: [ -x ${PREFIX}/sbin/thttpd_wrapper ] ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' I presume it was complaining about running a command in the background and then trying to use the operator to run the following command. -Clint To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
Clint Olsen wrote: Hi: I installed the port for thttpd, and when I upgraded to 4.7, it broke my rc.d script, complaining about an unexpected ''. The line it bitched about was something like: [ -x ${PREFIX}/sbin/thttpd_wrapper ] ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' I presume it was complaining about running a command in the background and then trying to use the operator to run the following command. check to see how ${PREFIX} is being evaluated: I have found quite a few rc scripts where it never worked: I just hard-coded the necessary values. -- Paul Beard / 8040 27th Ave NE / Seattle WA 98115 / paulbeard [at] mac [ dot] com / 206 529 8400 weblog @ http://paulbeard.no-ip.org/movabletype/ You're never too old to become younger. -- Mae West To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Nov 26, paul beard wrote: check to see how ${PREFIX} is being evaluated: I have found quite a few rc scripts where it never worked: I just hard-coded the necessary values. While I do agree with you, in this case it's not it. If I rewrote the script using an if statement, it worked just fine. if [ -x ${PREFIX}/sbin/thttpd_wrapper ]; then ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' fi -Clint To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Tue, Nov 26, 2002 at 09:14:18PM -0800, paul beard wrote: Clint Olsen wrote: Hi: I installed the port for thttpd, and when I upgraded to 4.7, it broke my rc.d script, complaining about an unexpected ''. The line it bitched about was something like: [ -x ${PREFIX}/sbin/thttpd_wrapper ] ${PREFIX}/sbin/thttpd_wrapper echo -n ' thttpd' I presume it was complaining about running a command in the background and then trying to use the operator to run the following command. check to see how ${PREFIX} is being evaluated: I have found quite a few rc scripts where it never worked: I just hard-coded the necessary values. No, it's the construction, which is illegal and should never have been allowed. Update to the latest version of the port and submit a PR if the bug persists. Kris msg10313/pgp0.pgp Description: PGP signature
Re: 4.7 changes to /bin/sh?
On Wednesday, November 27, 2002, at 12:25 AM, Kris Kennaway wrote: Hi: I installed the port for thttpd, and when I upgraded to 4.7, it broke my rc.d script, complaining about an unexpected ''. ${PREFIX}/sbin/thttpd_wrapper Funny that this should come up, as I recently upgraded to 4.7 and it broke my /usr/local/etc/rc.d/mysql-server.sh script with the same syntax? What changed? I tried a simple script on FreeBSD 4.7, OSX 10.2 and Solaris 8, and they all barfed on that syntax. my 2 pesos Brian -- Brian Jackson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: 4.7 changes to /bin/sh?
On Wed, Nov 27, 2002 at 12:38:03AM -0500, Brian Jackson wrote: On Wednesday, November 27, 2002, at 12:25 AM, Kris Kennaway wrote: Hi: I installed the port for thttpd, and when I upgraded to 4.7, it broke my rc.d script, complaining about an unexpected ''. ${PREFIX}/sbin/thttpd_wrapper Funny that this should come up, as I recently upgraded to 4.7 and it broke my /usr/local/etc/rc.d/mysql-server.sh script with the same syntax? What changed? I already told you in the section of my mail you deleted. Kris msg10323/pgp0.pgp Description: PGP signature