public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What to do with /var/run?
Date: Sun, 10 Feb 2013 14:14:16 -0500	[thread overview]
Message-ID: <19027.1360523656@ccs.covici.com> (raw)
In-Reply-To: <5117E9DF.7010404@binarywings.net>

Florian Philipp <lists@binarywings.net> wrote:

> Am 10.02.2013 19:01, schrieb covici@ccs.covici.com:
> > Florian Philipp <lists@binarywings.net> wrote:
> > 
> >> Am 10.02.2013 17:46, schrieb covici@ccs.covici.com:
> >>> Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> >>>
> >>>> On 10/02/2013 17:29, covici@ccs.covici.com wrote:
> >>>>> I had to actually prevent the migration to /run by changing the
> >>>>> boot.misc script because if I do not do that, a number of subdirectories
> >>>>> which I had created in /var/run were not in /run and a number of apps
> >>>>> would not start properly and indeed it is not taking much space, so I am
> >>>>> not sure why anyone bothered.  The only other option would have been to
> >>>>> write something to fix the /run, but that was not what I wanted  to do.
> >>>>> /var/lock had this same problem also.
> >>>>
> >>>> Why would you do that?
> >>>>
> >>>> /var/run is broken as the destination folder for what is intended to go
> >>>> in it, and it has been broken since day 1:
> >>>>
> >>>> /var/run is only available once /var is available or mounted.
> >>>> The contents of /var/run are often needed before /var is mounted.
> >>>> /run is the correct place for this.
> >>>>
> >>>> Problems with the migration are solved using the mv command
> >>>
> >>> But when I let the migration happen -- which was something udev or
> >>> openrc did -- then certain things in my runlevels would not start
> >>> because subdirectories in /var/run which were needed were missing and
> >>> had t o have correct owners and permissions.  /var/lock needed certain
> >>> subdirectories also such as news.  Only way to get them to work under
> >>> /run would be to have a script to run after boot.misc which created all
> >>> the subdirectories and fixed all the owners and permissions which is a
> >>> lot more work -- and it would of course have to be done on each reboot.
> >>>
> >> Are these init scripts from packages in the official tree, something you
> >> wrote yourself or some third-party package?
> >>
> >> In the first case, check if the problem persists (I bet it's fixed now)
> >> and file a bug report.
> >>
> >> In the second case, the best approach is to patch your scripts to use
> >> the `checkpath` command (see `man runscript`) to ensure that the
> >> expected paths exist.
> > 
> > As far as I remember, these are all packages from the tree and I am
> > using unstable, so I would have to file a number of bug reports.
> > There are a few things  such as freeswitch which I could fix in its
> > startup script, but here is the result of 
> > find /var/run -type d
> > and I would also have to fix owners and permissions unless the package
> > maintainers fix things.
> > 
> > /var/run/samba
> 
> https://bugs.gentoo.org/show_bug.cgi?id=454676
> 
> > /var/run/dbus
> 
> https://bugs.gentoo.org/show_bug.cgi?id=387897
> Fixed in stable.
> 
> > /var/run/named
> 
> https://bugs.gentoo.org/show_bug.cgi?id=334535
> Fixed in stable.
> 
> > /var/run/fail2ban
> 
> https://bugs.gentoo.org/show_bug.cgi?id=449966
> Fixed without a revision bump.
> 
> > /var/run/asterisk
> 
> https://bugs.gentoo.org/show_bug.cgi?id=451808
> https://bugs.gentoo.org/show_bug.cgi?id=445182
> https://bugs.gentoo.org/show_bug.cgi?id=450222
> Fixed in stable.
> 
> > /var/run/freeswitch
> 
> Guess this goes nowhere with maintainer-needed status.
> https://bugs.gentoo.org/show_bug.cgi?id=150527
> 
> > /var/run/wpa_supplicant
> 
> https://bugs.gentoo.org/show_bug.cgi?id=387895
> Works for me with /var/run symlink.
> 
> > /var/run/gdm
> > /var/run/gdm/greeter
> > /var/run/gdm/auth-for-gdm-GtotHP
> 
> Should work or more people would complain.
> 
> > /var/run/openldap
> 
> https://bugs.gentoo.org/show_bug.cgi?id=444912
> Fixed in testing.
> 
> > /var/run/dhcpcd
> > /var/run/dhcpcd/ntp.conf
> > /var/run/dhcpcd/resolv.conf
> 
> Works for me.
> 
> > /var/run/pulse
> 
> https://bugs.gentoo.org/show_bug.cgi?id=442852
> 
> > /var/run/mysqld
> 
> Works for me.
> 
> > /var/run/cups
> 
> https://bugs.gentoo.org/show_bug.cgi?id=451756
> Works for me.
> 
> > /var/run/cups/certs
> 
> https://bugs.gentoo.org/show_bug.cgi?id=387893
> Fixed in stable.
> 
> > /var/run/radvd
> 
> https://bugs.gentoo.org/show_bug.cgi?id=453140
> Fixed in stable.
> 
> > /var/run/pm-utils
> > /var/run/pm-utils/locks
> > /var/run/pm-utils/pm-powersave
> > /var/run/pm-utils/pm-powersave/storage
> 
> Works for me.
> 
> > /var/run/proftpd
> 
> https://bugs.gentoo.org/show_bug.cgi?id=449360
> https://bugs.gentoo.org/show_bug.cgi?id=387889
> Fixed in testing.
> 
> > /var/run/dhcp
> 
> https://bugs.gentoo.org/show_bug.cgi?id=446446
> Fixed in stable.
> 
> > /var/run/udisks
> 
> https://bugs.gentoo.org/show_bug.cgi?id=333893
> Fixed in stable.
> 
> > /var/run/spamd
> 
> https://bugs.gentoo.org/show_bug.cgi?id=455604
> 
> > /var/run/ConsoleKit
> 
> https://bugs.gentoo.org/show_bug.cgi?id=450224
> https://bugs.gentoo.org/show_bug.cgi?id=387901
> 
> Works for me.
> 
> > /var/run/console
> 
> Works for me.

Thanks -- I will have to investigate the ones you say are fixed and see
why they didn't work or which ones did not.  Innd is another matter with
its wanting /var/lock/news and the /var/lock permissions were wrong, but
I can fix that.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com


  reply	other threads:[~2013-02-10 19:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  5:11 [gentoo-user] What to do with /var/run? Grant
2013-02-10  6:47 ` J. Roeleveld
2013-02-10  7:04   ` J. Roeleveld
2013-02-10  8:28 ` Florian Philipp
2013-02-10 11:49   ` Michael Mol
2013-02-10 12:40     ` Alan McKinnon
2013-02-10 13:14       ` Michael Mol
2013-02-10 13:33         ` Alan McKinnon
2013-02-10 13:42         ` Florian Philipp
2013-02-10 17:58           ` Neil Bothwick
2013-02-10 15:29         ` covici
2013-02-10 15:55           ` Alan McKinnon
2013-02-10 16:46             ` covici
2013-02-10 17:03               ` Florian Philipp
2013-02-10 18:01                 ` covici
2013-02-10 18:41                   ` Florian Philipp
2013-02-10 19:14                     ` covici [this message]
2013-02-10 20:54                   ` Alan McKinnon
2013-02-10 21:41                     ` covici
2013-02-10 15:53       ` Dale
2013-02-10 15:56         ` Alan McKinnon
2013-02-10 16:39           ` Dale
2013-02-10 16:56             ` Florian Philipp
2013-02-10 17:39               ` Dale
2013-02-10 17:56               ` Neil Bothwick
2013-02-10 18:00                 ` Florian Philipp
2013-02-10 19:17                 ` Grant
2013-02-10 19:42                   ` Florian Philipp
2013-02-16 20:08                     ` Grant
2013-02-16 23:28                       ` Florian Philipp
2013-02-10 13:14     ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19027.1360523656@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox