Skip to main content

Extract username from netgroup output

I have NO idea how portable this is, whether it would work in an environment other than my own, etc...  So - give it a try, let me know if you found some place it would not work and how you fixed it.

This is a HACK.  Someone could do this with Perl/Python/etc... and make lightwork of the problem.  That was not a possible solution for what I was trying to do.

So - I would like to automate a job to take the users who belong to a particular netgroup and apply filesystem quotas to those users.  Unfortunately, the output from a getent command is a bit difficult to simply parse.

I am going to create a file with the output of the getent command (not necessary)
[jradtke@cypher BashFoo]$ getent netgroup sysadmin > netgroup.sysadmin
sysadmin              ( , jradtke, ) ( , usern1, )  ( , dilbert, )

Remove the name of the netgroup itself from my query
[jradtke@cypher BashFoo]$ cat netgroup.sysadmin | sed 's/sysadmin//g'
              ( , jradtke, ) ( , usern1, )  ( , dilbert, )

This next step is a total hack, I replace the the trailing parenthesis ) with a newline character
[jradtke@cypher BashFoo]$ cat netgroup.sysadmin | sed 's/sysadmin//g' | sed 's/)/\n/g'
              ( , jradtke,
 ( , usern1,
  ( , dilbert,

I then display the 2nd field using the comma ',' as my Field Seperator
[jradtke@cypher BashFoo]$ cat netgroup.sysadmin | sed 's/sysadmin//g' | sed 's/)/\n/g' | awk 'BEGIN {FS=","}{print $2}'
 jradtke
 usern1
 dilbert

Lastly - I remove the leading space before each name
[jradtke@cypher BashFoo]$ cat netgroup.sysadmin | sed 's/sysadmin//g' | sed 's/)/\n/g' | awk 'BEGIN {FS=","}{print $2}' | grep -v ^$
 jradtke
 usern1
 dilbert

[jradtke@cypher BashFoo]$ cat netgroup.sysadmin | sed 's/sysadmin//g' | sed 's/)/\n/g' | awk 'BEGIN {FS=","}{print $2}' | grep -v ^$ | sed 's/\ //g'
jradtke
usern1
dilbert

Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...