Return-Path: X-Original-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6DEB09766 for ; Tue, 12 Jun 2012 00:37:01 +0000 (UTC) Received: (qmail 4463 invoked by uid 500); 12 Jun 2012 00:37:00 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 4397 invoked by uid 500); 12 Jun 2012 00:37:00 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 4303 invoked by uid 99); 12 Jun 2012 00:37:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jun 2012 00:37:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [66.246.75.169] (HELO smartechhomes.com) (66.246.75.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jun 2012 00:36:54 +0000 Received: from pool-173-79-237-188.washdc.fios.verizon.net ([173.79.237.188] helo=[206.223.85.7]) by smartechhomes.com with esmtpa (Exim 4.72 #1 (Debian)) id 1SeF5v-0002je-4l for ; Mon, 11 Jun 2012 20:36:32 -0400 Message-ID: <4FD68F02.4060708@smartechhomes.com> Date: Mon, 11 Jun 2012 20:36:18 -0400 From: Jerry Stuckle User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: modules-dev@httpd.apache.org References: <4FD67F10.2080702@smartechhomes.com> <4FD68706.2030707@smartechhomes.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 173.79.237.188 X-SA-Exim-Mail-From: jerry@smartechhomes.com X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smartechhomes.com X-Spam-Level: Subject: Re: Get the directory of the module X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on smartechhomes.com) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 But how would he know where his .conf file is installed? If he could find where his .conf file is installed, he could just put the data there. On 6/11/2012 8:19 PM, Joshua Marantz wrote: > I think we are saying the same thing, right? To "tell his module" I'm > suggesting he write the path where the .so is installed into his .conf file > so that he can get the path at runtime. > > On Mon, Jun 11, 2012 at 8:02 PM, Jerry Stucklewrote: > >> In that case he should also be able to tell his module where the files are. >> >> >> On 6/11/2012 7:40 PM, Joshua Marantz wrote: >> >>> I think he wants to write bytecodes during module installation when he >>> will >>> have write access. >>> >>> During installation can you also write a .conf template showing your >>> module >>> where the bytecodes are? >>> >>> Josh >>> On Jun 11, 2012 7:29 PM, "Jerry Stuckle"> >>> wrote: >>> >>> >>>> >>>> On 6/11/2012 5:49 PM, Ben Noordhuis wrote: >>>> >>>> On Mon, Jun 11, 2012 at 10:10 PM, Bart Wiegmans>>>> com> >>>>> >>>>> wrote: >>>>> >>>>> Hello everybody, >>>>>> >>>>>> For a project I'm doing, I need to install a few bytecode files >>>>>> alongside my module. I was planning on placing them in the modules >>>>>> directory but I realised that at runtime I do not know where that is. >>>>>> What is more, that directory may (and will, as a matter of fact) vary >>>>>> during installation and testing. But most importantly, the server >>>>>> knows where the module is kept as it specified by LoadModule. >>>>>> >>>>>> So in short, how can I determine the directory of my module at runtime? >>>>>> >>>>>> >>>>> You can't, the file path is internal to mod_so.c. I don't think it >>>>> even stores it. >>>>> >>>>> >>>>> >>>>> In addition, there is no guarantee you have write access to that >>>> directory. >>>> >>>> >>> >