Re: [systemd-devel] System units packaging and rpmlint

2013-05-18 Thread Andrey Borzenkov
В Sat, 18 May 2013 23:44:48 +0200 Michael Scherer пишет: > > So I planned to warn if the unit are directly in /lib, but I know there > is some distribution that didn't choose this path yet. So when /usr is > not merged, what is the canonical location ( ie, for Opensuse, Mandriva, > since they ar

Re: [systemd-devel] System units packaging and rpmlint

2013-05-18 Thread David Strauss
I'm skipping to the questions I can answer. On Sat, May 18, 2013 at 2:44 PM, Michael Scherer wrote: > - we should avoid as much as possible to use Type=forking when we can > avoid it. > > This one is likely the one that will be met with resistance from > packagers, so before adding it as warning,

Re: [systemd-devel] systemd-cgroups-agent failed to get dbus connection

2013-05-18 Thread Ross Lagerwall
On Tue, May 07, 2013 at 09:31:58AM +0100, Ross Lagerwall wrote: > I have noticed sometimes during shutdown, the following message appears > on screen twice: > systemd-cgroups-agent failed to get dbus connection: failed to connect > to socket /org/freedesktop/systemd/private connection refused > >

[systemd-devel] System units packaging and rpmlint

2013-05-18 Thread Michael Scherer
Hi, After the last discussion on fedora-devel about boot times[1], I have been looking at the various units on my disk and if I could code something in rpmlint ( tool to verify a rpm against a set of guidelines ) to have packagers follow some best practices. So I have been writing various checks

Re: [systemd-devel] build problems without largefile support

2013-05-18 Thread David Strauss
On Wed, May 15, 2013 at 11:49 PM, Michael Olbrich wrote: > The constants for T/P/E don't fit in a 23bit off_t. That's why largefile > was introduced in the first place. > I'm not sure how to fix this. Maybe just use 'ifdef' and not support those > formats? That sounds reasonable to me. The lack o

Re: [systemd-devel] Trusting systemd vs. trusting daemons

2013-05-18 Thread David Strauss
On Thu, May 16, 2013 at 11:39 PM, Aaron Faanes wrote: > So my question, simply, is this: Should I prefer running a process as > root knowing that it chroots itself, or should I run it as non-root > and chroot it via systemd? I support the "trust systemd; don't trust the daemon" model going forwar