Useless "group system does not exist - using root" messages

IBM / ibmichroot

A set of scripts to facilitate the use of chroot-based containers for IBM i

MIT License

21 stars 9 forks source link

Useless "group system does not exist - using root" messages #11

Closed abmusse closed 8 years ago

abmusse commented 9 years ago

Original report by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

Seeing a lot of these because of the -v option on the rpm command (hundreds on the git install).

group system does not exist - using root

Am wondering if we should remove the -v option and just stick with -hU which still gives us the name of the rpm being installed (with hash progress). I am assuming errors would still be communicated even without -v being specified.

Thoughts?

abmusse commented 8 years ago

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

Yes. We are using AIX RPMs, Perzl, AIX Toolbox. Sometimes just easier to go with flow of AIX.

System special user accounts

#!shell

Create a group profile(s):

CRTUSRPRF USRPRF(SYSTEM) PASSWORD(*NONE) USRCLS(*SYSOPR) TEXT('AIX rpm group') SPCAUT(*USRCLS) GID(*GEN) AUT(*ALL)

CRTUSRPRF USRPRF(BIN) PASSWORD(*NONE) USRCLS(*SYSOPR) TEXT('AIX rpm group') SPCAUT(*USRCLS) GID(*GEN) AUT(*ALL)

Note: You may choose authorization settings.

This is optional. Install rpm message is not fatal installing AIX RPMs on IBM i. Also, not an issue for folks that use IBM i only RPMs, PTFs, etc. However, personally, i am in favour of joining larger community of AIX RPMs, widen our IBM i pond of RPM resources beyond our smaller IBM i community. All users will have to decide, but best to have options available.

abmusse commented 8 years ago

Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

I realize this issue is closed but I wanted to document for those coming here after the fact.

Tony made this commit that addresses the issue by adding user profiles being looked for.

abmusse commented 9 years ago

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

yep, just to record for later ... possibly scsan/filter on fly using stderr redirect 2>&1, but again low priority (me thinks).

abmusse commented 9 years ago

Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

The only way I can think to turn it off would be to route it to a temp file, sanitize for messages we don't want to see, and then put the sanitized result back to stdout. I am not a huge fan of this approach. I think this is a very low priority given its complications.

abmusse commented 9 years ago

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

i not sure silence is golden ... not easy to turn off, AIX binaries with AIX group thinking we force onto PASE. I am thinking no action here, unless better case made.

abmusse commented 9 years ago

Original comment by PHPDave (Bitbucket: PHPDave, GitHub: PHPDave).

I was confused about that message when i installed rpms. Would be nice if you could remove it to avoid confusion.

abmusse commented 9 years ago

Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

Nevermind. I tried taking the -v option off rpm and it didn't remove the group system does not exist - using root messages and instead only altered the hash logging to omit the name of the package being installed.

Closing issue.

abmusse commented 9 years ago

Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

Maybe we could add a verbose on/off option to chroot_setup.sh and pkg_setup.sh?

abmusse commented 9 years ago

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

Dunno. Sort of a verbose or not (eye of beholder). BTW -- i am out this afternoon, back tomorrow, then out next week.