From: "Dmitry V. Levin" <ldv@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] [cyber] I: Sisyphus-20221222 x86_64 beehive_status: +37 -3 (101)
Date: Fri, 23 Dec 2022 18:51:22 +0300
Message-ID: <20221223155122.GC26671@altlinux.org> (raw)
In-Reply-To: <20221223154721.GB26671@altlinux.org>
On Fri, Dec 23, 2022 at 06:47:21PM +0300, Dmitry V. Levin wrote:
> On Fri, Dec 23, 2022 at 04:42:04PM +0100, Alexey Gladkov wrote:
> > On Fri, Dec 23, 2022 at 06:26:31PM +0300, Dmitry V. Levin wrote:
> > > On Thu, Dec 22, 2022 at 02:01:18PM +0300, Dmitry V. Levin wrote:
> > > > On Thu, Dec 22, 2022 at 01:33:30PM +0300, Валерий Иноземцев wrote:
> > > > > 22.12.2022 13:26, Dmitry V. Levin пишет:
> > > > > > On Thu, Dec 22, 2022 at 12:05:56PM +0300, Валерий Иноземцев wrote:
> > > > > >> 22.12.2022 11:25, Dmitry V. Levin пишет:
> > > > > >>> On Thu, Dec 22, 2022 at 08:10:27AM +0000, ALT beekeeper wrote:
> > > > > >>>> 37 NEW error logs
> > > > > >>> [...]
> > > > > >>>> xdg-dbus-proxy-0.1.4-alt1
> > > > > >>>> dbus-daemon[4180584]: Failed to start message bus: Failed to bind socket
> > > > > >>>> "/run/dbus/users/dbus-DkOyMz7clK": No such file or directory
> > > > > >>>
> > > > > >>> Что-то массово сломалось после обновления пакета dbus?
> > > > > >>
> > > > > >> да. см. аттач
> > > > > >> какие предложения? откатывать a70b042f?
> > > > > >
> > > > > > Альтернативно, может быть, что-то в системе должно создавать /run/dbus/users/ ?
> > > > > > Хотя наличие по умолчанию в системе каталога /run/dbus/users/, доступного
> > > > > > всем на запись, что позволяет легко устроить DoS на /run/, тоже не
> > > > > > выглядит хорошей идеей.
> > > > >
> > > > > для этого есть /lib/tmpfiles.d/dbus.conf
> > > > > d /run/dbus 0755 root root -
> > > > > d /run/dbus/users 1777 root root -
> > > > >
> > > > > в hasher это не работает
> > > >
> > > > Если в системе присутствует пакет systemd или systemd-utils-standalone,
> > > > то /usr/lib/rpm/systemd-tmpfiles.filetrigger из пакета
> > > > systemd-utils-filetriggers обрабатывает эти файлы.
> > >
> > > Обрабатывать-то оно обрабатывает, однако
> > > $ hsh-run --root -- systemd-tmpfiles --create; echo $?
> > > /proc/ is not mounted, but required for successful operation of systemd-tmpfiles. Please mount /proc/. Alternatively, consider using the --root= or --image= switches.
> > > 1
> >
> > Эм. А зачем ему /proc ???
>
> Оно утверждает, будто "for successful operation", что бы это ни значило. :)
https://github.com/systemd/systemd/commit/01131684ac6
/* We require /proc/ for a lot of our operations, i.e. for adjusting access modes, for anything
* SELinux related, for recursive operation, for xattr, acl and chattr handling, for btrfs stuff and
* a lot more. It's probably the majority of invocations where /proc/ is required. Since people
* apparently invoke it without anyway and are surprised about the failures, let's catch this early
* and output a nice and friendly warning. */
--
ldv
next prev parent reply other threads:[~2022-12-23 15:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 8:25 ` Dmitry V. Levin
2022-12-22 9:05 ` Валерий Иноземцев
2022-12-22 9:42 ` Валерий Иноземцев
2022-12-22 10:26 ` Dmitry V. Levin
2022-12-22 10:33 ` Валерий Иноземцев
2022-12-22 11:01 ` Dmitry V. Levin
2022-12-23 15:26 ` Dmitry V. Levin
2022-12-23 15:42 ` Alexey Gladkov
2022-12-23 15:47 ` Dmitry V. Levin
2022-12-23 15:51 ` Dmitry V. Levin [this message]
2022-12-23 16:16 ` Alexey Gladkov
2022-12-23 15:52 ` Alexey Gladkov
2022-12-24 13:38 ` Mikhail Efremov
2023-01-10 14:04 ` Mikhail Efremov
2023-01-10 17:16 ` Dmitry V. Levin
2022-12-22 11:12 ` Arseny Maslennikov
2022-12-22 11:16 ` Валерий Иноземцев
2022-12-22 11:21 ` Sergey V Turchin
2022-12-22 11:40 ` Dmitry V. Levin
2022-12-22 11:45 ` Sergey V Turchin
2022-12-22 11:59 ` Антон Мидюков
2022-12-22 12:29 ` Sergey V Turchin
2022-12-22 12:33 ` Валерий Иноземцев
2022-12-22 12:40 ` Sergey V Turchin
2022-12-22 12:55 ` Валерий Иноземцев
2022-12-22 13:06 ` Sergey V Turchin
2022-12-22 13:21 ` Валерий Иноземцев
2022-12-22 13:53 ` Sergey V Turchin
2022-12-22 13:12 ` Антон Мидюков
2022-12-22 13:15 ` Dmitry V. Levin
2023-02-28 13:54 ` Stanislav Levin
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=20221223155122.GC26671@altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git