Summary: | mysqld fails to start on tmpfs mounted /var/run (can't find /var/run/mysqld) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joshua Rich <joshua.rich> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | CC: | d.h.j.takken |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joshua Rich
2007-05-09 00:21:28 UTC
Sorry, if you moved /var/run to a volatile filesystem, it's up to you to make sure the needed dirs get created/bind-mounted or whatever. mysql.eclass already creates the directory, incl. the needed permissions. And note that /var/run subdirectories completely wiped on reboot will break lots more than just mysql. Ah, I see. There appears to be confusing and/or conflicting views as to whether /var/run can be mounted in this way. If you say it breaks other stuff then I guess that is a bad thing, I take it Gentoo expects a non-volatile /var/run in a few programs. In that case, away with tmpfs! Thanks for the quick response! Josh Well, at least hal, dbus, samba, nscd, vmware, screen and sudo expect the dirs to be there with appropriate permissions (only the stuff that I have installed here, there's definitely more). # ls -lAd $(find /var/run -maxdepth 1 -type d) drwxr-xr-x 12 root root 2312 2007-05-08 19:25 /var/run drwxr-xr-x 2 avahi avahi 96 2007-05-08 18:54 /var/run/avahi-daemon drwxr-xr-x 3 root lp 104 2007-05-08 18:54 /var/run/cups drwxr-xr-x 2 root root 88 2007-05-08 18:54 /var/run/dbus drwxr-xr-x 4 haldaemon haldaemon 112 2007-04-27 23:57 /var/run/hald drwxr-xr-x 2 root root 96 2007-05-08 18:54 /var/run/nscd drwxr-xr-x 2 root root 96 2007-05-08 18:54 /var/run/samba drwxr-xr-x 4 root root 96 2006-11-04 01:13 /var/run/screen drwx------ 3 root root 72 2006-11-10 13:10 /var/run/sudo drwxr-xr-x 2 tor tor 72 2007-05-08 18:55 /var/run/tor drwxr-xr-x 3 root root 144 2007-05-08 19:25 /var/run/vmware So, I really don't think it's a good idea to wipe the dir on every reboot. :) *** Bug 188543 has been marked as a duplicate of this bug. *** |