From owner-freebsd-questions@FreeBSD.ORG Sun Feb 9 00:24:06 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA89BEDB for ; Sun, 9 Feb 2014 00:24:06 +0000 (UTC) Received: from mail-qc0-f169.google.com (mail-qc0-f169.google.com [209.85.216.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 959161CF1 for ; Sun, 9 Feb 2014 00:24:06 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id w7so8494955qcr.14 for ; Sat, 08 Feb 2014 16:24:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=s1Fe0SToCnbCjg5PdtcfGepESkV62kTyIdysmQT9TYc=; b=QipFIur//8enlJgU2e794eoF9+JDffN09s5nFiufPCeapCT+ha+cIkKA/yaC3p+kK2 kXwD83M+6bTPW6lb1Zx58VxuQ5JMZTytHCFkIZI5kAWXXL1CjS67R/fNkGIg/x0W/C+Q YaaryYEyat0e0E3O8XbtKC3fPMe2f24+t+JR0rU3tlXZhuB8ZXqeBwVLqHypUpm/U890 t0Th+OAPc1yNPh9nzDA5h4mhkvoWYY4Gl7Va3wSy9CHJnvoBhklFjoBMGKfkzDu3klXr EVZu6a/V1YOs9bDyNu2fJ+g8mKQpIEmo5q3/GHRWcjMMDocnTpC6LG3RmztYzgjy9yf/ rpog== X-Gm-Message-State: ALoCoQlo7Lvyp1md49ae8AUsq9rKGl8CIDIXZgVY9NumhhtbryiTj/UQp6BDZNfpoBK8AnfeRxG3 X-Received: by 10.224.66.134 with SMTP id n6mr34889517qai.39.1391905445269; Sat, 08 Feb 2014 16:24:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.40.231 with HTTP; Sat, 8 Feb 2014 16:23:45 -0800 (PST) X-Originating-IP: [96.20.160.26] In-Reply-To: <6E5755D9-2A53-4B32-BAD0-D4BDC98D5CB9@w21.org> References: <437A267C-F698-4FF1-A4BF-C63634540F19@w21.org> <6E5755D9-2A53-4B32-BAD0-D4BDC98D5CB9@w21.org> From: Iqbal Aroussi Date: Sat, 8 Feb 2014 19:23:45 -0500 Message-ID: Subject: Re: NSD 4.0.1 wont start after upgrad To: Juergen Nickelsen Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 00:24:07 -0000 On Sat, Feb 8, 2014 at 6:45 PM, Juergen Nickelsen wrote: > On 2014-02-08, at 21:07, Iqbal Aroussi wrote: > > > nsd_enable to YES is already in rc.conf > > But apparently it is not in /usr/local/etc/rc.d/nsd, hence the error > message. > > If it is really set /etc/rc.conf (I trust you re-checked that), you'll > have to figure out where it where it gets lost. I usually investigate such > problems by liberally sprinkling statements like "echo > nsd_enable=$nsd_enable" all over the place, i.e. in the relevant places in > all scripts involved. > > Regards, Juergen. > Hi Juergen, Yes I verified twice. and nsd_enable is set to YES in my /etc/rc.conf file. I compared the two rc scripts for nsd 4.0.0 and 4.0.1 and there is a lot of missing lines in the new version. Unfortunately, I'm not rc scripts expert so I substituted the new /usr/local/etc/rc.d/nsd by old content and it works as expected. Regards Iqbal From owner-freebsd-questions@FreeBSD.ORG Sun Feb 9 05:03:11 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EEF35AC for ; Sun, 9 Feb 2014 05:03:11 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1310143C for ; Sun, 9 Feb 2014 05:03:10 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id l4so3821200lbv.19 for ; Sat, 08 Feb 2014 21:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=WPPTHHgaz5xOJcPETJfXUNXTrk9/45FhwsehCko9Nhw=; b=y0kroqePK4BLTPhdNg6a6biiTaYHEiG5tHOZLLOFztE9/nwXAXpzdtnpJvWYrxpFQr nO3iky5500y9YG7nRjVZZNJY1tnEdRfSV+UrVcFkMC0vx5I/l16cyoYIbuc8yOM0Ds55 rulXX44PwubE2vll6bmMK2T+UHdyObGKe6Drc6QzCzAGeKa6zJK8618g3nCQVeWaM5d6 zgJmtXB9EH/SQUsverQAS72646hE0i/quCNO7WBXAGIaXJ6yFSWliomDAPh9UdmxXEmF Ys5HyifD0+bc/iNzo29KEq2lOilYGEqyDt9+BipNI8XZpJHR8wkqe8dh4ZgA6ErqQQ27 5cFw== MIME-Version: 1.0 X-Received: by 10.112.137.65 with SMTP id qg1mr15778265lbb.7.1391922188007; Sat, 08 Feb 2014 21:03:08 -0800 (PST) Received: by 10.152.203.233 with HTTP; Sat, 8 Feb 2014 21:03:07 -0800 (PST) Date: Sat, 8 Feb 2014 21:03:07 -0800 Message-ID: Subject: UWSGI from INI From: Sergei G To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 05:03:11 -0000 Hi, several months ago I adjusted uwsgi script to load most of its configuration from INI file instead of rc.conf file. It utilizes all of uwsgi properties this way. Do you think it is worth posting it to make available to greater audience? I called it uwsgiini. Here is the source code: #!/bin/sh # # PROVIDE: uwsgiini # REQUIRE: DAEMON # KEYWORD: shutdown # # Add the following lines to /etc/rc.conf to enable uwsgi: # # uwsgiini_enable (bool): Set it to "YES" to enable uwsgi # Default is "NO". # # If you would like to have multiple uWSGI instances running, you can # define multiple profiles: # # uwsgiini_profiles (str): Set the list of uwsgi profiles # Default is "". # # For each profile you can then define different options (except for # uwsgiini_enable) using the syntax uwsgi__