On Mon, 07.07.14 13:16, Leonid Isaev ([email protected]) wrote:
> On Mon, Jul 07, 2014 at 05:40:42PM +0200, Lennart Poettering wrote:
> > On Mon, 07.07.14 11:08, Leonid Isaev ([email protected]) wrote:
> >
> > > Hi,
> > >
> > > Thanks for the explanation...
> > >
> > > On Mon, Jul 07, 201
On Mon, Jul 07, 2014 at 05:40:42PM +0200, Lennart Poettering wrote:
> On Mon, 07.07.14 11:08, Leonid Isaev ([email protected]) wrote:
>
> > Hi,
> >
> > Thanks for the explanation...
> >
> > On Mon, Jul 07, 2014 at 12:26:03PM +0200, Lennart Poettering wrote:
> > > I wasn#t aware of grpck, a
On Mon, 07.07.14 11:08, Leonid Isaev ([email protected]) wrote:
> Hi,
>
> Thanks for the explanation...
>
> On Mon, Jul 07, 2014 at 12:26:03PM +0200, Lennart Poettering wrote:
> > I wasn#t aware of grpck, and quite frankly don't think it makes much
> > sense, what the tool is doing.
>
Hi,
Thanks for the explanation...
On Mon, Jul 07, 2014 at 12:26:03PM +0200, Lennart Poettering wrote:
> I wasn#t aware of grpck, and quite frankly don't think it makes much
> sense, what the tool is doing.
Why? Checking syntax can never hurt...
> > Does it mean that on each update, a p
On Sun, 06.07.14 19:17, Leonid Isaev ([email protected]) wrote:
> Hi,
>
> Shouldn't systemd-sysusers update /etc/gshadow when adding 'basic'
> groups? From sysusers.c I don't see that gshadow (and shadow) is updated, and
> this seems to cause problems on package updates. Consider the foll
Hi,
Shouldn't systemd-sysusers update /etc/gshadow when adding 'basic'
groups? From sysusers.c I don't see that gshadow (and shadow) is updated, and
this seems to cause problems on package updates. Consider the following
scenario:
1. A package is updated, so timestamp of /usr gets ahead of
