Hmm, I've just looked at this patch with the intent of sponsoring it, but have some remaining concerns.
Using the debian-sys-maint account (and therefore forcing root) , which is what --local does, seems sub-par; this user has more permissions than are actually needed to run mtop and therefore there are potential security risks. Is there any reason why dbconfig-common[0] can't be used properly to create the user? From a brief reading it seems like there's just a problem with the way dbconfig-common is used that could be fixed.
You removed the --idle option from the help output. Was that intentional?
README.Debian will need updating with whatever solution we go for.
Hmm, I've just looked at this patch with the intent of sponsoring it, but have some remaining concerns.
Using the debian-sys-maint account (and therefore forcing root) , which is what --local does, seems sub-par; this user has more permissions than are actually needed to run mtop and therefore there are potential security risks. Is there any reason why dbconfig-common[0] can't be used properly to create the user? From a brief reading it seems like there's just a problem with the way dbconfig-common is used that could be fixed.
You removed the --idle option from the help output. Was that intentional?
README.Debian will need updating with whatever solution we go for.
[0] http:// people. debian. org/~seanius/ policy/ dbconfig- common. html/