[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /run and needing a --rundir for configure
From: |
Paolo Bonzini |
Subject: |
Re: /run and needing a --rundir for configure |
Date: |
Tue, 10 Sep 2013 09:03:40 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8 |
Il 10/09/2013 01:17, Karl Berry ha scritto:
> Does this additional text suit everyone? (Before I send it back to rms.)
>
> k
>
> @item rundir
> The directory for installing data files which the programs modify
> while they run, that pertain to one specific machine, and which need
> not persist longer than the execution of the program---which is
> generally long-lived, for example, until the next reboot. PID files
> for system daemons are a typical use. In addition, this directory
> should not be cleaned except perhaps at reboot, while the general
> @file{/tmp} (@code{TMPDIR}) may be cleaned arbitrarily. This should
> normally be @file{/var/run}, but write it as
> @file{$(localstatedir)/run}. (Having it as a separate variable allows
> the use of @file{/run} if desired). (If you are using Autoconf 2.70
> or later, write it as @samp{@@rundir@@}.)
> @end table
>
>
>
Perhaps:
This should normally be @samp{$(localstatedir)/run}, but having a
separate variable allows the user to customize it separately from
@env{localstatedir}, for example to use @file{/run}. If you are using
Autoconf 2.70 or later, write it as @samp{@@rundir@@}.
Paolo
- Re: /run and needing a --rundir for configure, (continued)
Re: /run and needing a --rundir for configure, Karl Berry, 2013/09/09
Re: /run and needing a --rundir for configure, Karl Berry, 2013/09/13
Re: /run and needing a --rundir for configure, Paolo Bonzini, 2013/09/14
Re: /run and needing a --rundir for configure, Karl Berry, 2013/09/11