> Usermod is only called if the user does not exist and the package creates
> it. gdm, postgresql and logcheck already do this. In the example code,
> if the system user exists, then usermod is not called, which is better than
> what logcheck or postgresl currently do.
One very short notice for i
On Tue, Nov 01, 2005 at 12:14:58PM +0100, Jonas Meurer wrote:
> On 31/10/2005 Javier Fernández-Sanguino Peña wrote:
> > After the feedback of the recent d-d thread, I've adapted the section I
> > wrote
> > on the best practices related to system users and groups, it is currently
> > available at:
On Tue, Nov 01, 2005 at 04:53:33AM -0500, sean finney wrote:
> hi javier,
>
> On Mon, Oct 31, 2005 at 10:03:01PM +0100, Javier Fernández-Sanguino Peña
> wrote:
> > I would like developers to review and provide feedback for that section,
>
> thanks for actually putting this into a document, howev
On Tue, Nov 01, 2005 at 11:10:19AM +0100, Olaf van der Spek wrote:
> ma, 2005-10-31 kello 22:03 +0100, Javier Fernández-Sanguino Peña
> kirjoitti:
> > I would like developers to review and provide feedback for that section,
> > specially in form of patches. I'm considering doing a bug hunt for:
>
On Tue, Nov 01, 2005 at 11:14:59AM +0200, Lars Wirzenius wrote:
> ma, 2005-10-31 kello 22:03 +0100, Javier Fernández-Sanguino Peña
> kirjoitti:
> > After the feedback of the recent d-d thread, I've adapted the section I
> > wrote
> > on the best practices related to system users and groups, it is
On Tue, Nov 01, 2005 at 11:14:59AM +0200, Lars Wirzenius wrote:
> Also, sticking all the tens of lines of boilerplate code into the
> postinst of every package that needs a system user is a good way to
> invite trouble. When the boilerplate has a bug (possibly because things
> change in the future)
On Tue, 1 Nov 2005 04:53:33 -0500, sean finney <[EMAIL PROTECTED]>
wrote:
>if you're going to do this, it would be better to provide a program
>or a shell library that is sourced in the postinst, and then
>awrapper function which does all of this.
I would be willing to accept patches for the add
On 01/11/2005 To Debian-Devel wrote:
> the group deletion has currently a problem. From 6.5.1.3 'Removing system
> users':
>
> # Remove system group if is a system group
> CREATEDGROUP=server_group
> if [ -r /etc/adduser.conf ] ; then
> FIRST_USER_GID=`grep ^USERS_GID /etc/adduser.conf | cut -f2
On 31/10/2005 Javier Fernández-Sanguino Peña wrote:
> After the feedback of the recent d-d thread, I've adapted the section I wrote
> on the best practices related to system users and groups, it is currently
> available at:
> http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-pra
ma, 2005-10-31 kello 22:03 +0100, Javier Fernández-Sanguino Peña
kirjoitti:
> I would like developers to review and provide feedback for that section,
> specially in form of patches. I'm considering doing a bug hunt for:
> Typically this means that the configuration files are owned by group, belon
hi javier,
On Mon, Oct 31, 2005 at 10:03:01PM +0100, Javier Fernández-Sanguino Peña wrote:
> I would like developers to review and provide feedback for that section,
thanks for actually putting this into a document, however, i notice
two problems:
- the addgroup/adduser functions mask the error
ma, 2005-10-31 kello 22:03 +0100, Javier Fernández-Sanguino Peña
kirjoitti:
> After the feedback of the recent d-d thread, I've adapted the section I wrote
> on the best practices related to system users and groups, it is currently
> available at:
> http://www.debian.org/doc/manuals/developers-refe
After the feedback of the recent d-d thread, I've adapted the section I wrote
on the best practices related to system users and groups, it is currently
available at:
http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-lower-privs
I would like developers t
13 matches
Mail list logo
