Sponsored Content
Full Discussion: Frustrating Groups loop
Top Forums Shell Programming and Scripting Frustrating Groups loop Post 302669331 by Chubler_XL on Wednesday 11th of July 2012 12:40:26 AM
Old 07-11-2012
The "no such user" message is probably being output to stderr to capture it you will need to redirect stderr to stdout like this:
Code:
USER_HAS_GROUPS="`id $i 2>&1`"

Here is another thought, why not examine the return value from the id command something along the lines of this:
Code:
while read i
  if id $i > /dev/null 2>&1
  then
    USER_LDAP_GROUPS="`id $i | cut -d\= -f4 | sed 's/([^()]*)//g;s/,/ /g'`"
    echo $USER_LDAP_GROUPS
  else
     echo "Invalid user $i"
  fi
done < txt1

 

10 More Discussions You Might Find Interesting

1. Linux

Frustrating!

Hi All I have an extremely frustrating problem with my Mandrake 9.1 machine. When I am in KDE no browser at all will resolve hostnames. Networking is fine, as I can reach websites via IP address, however hostnames just don't work! When I conduct 'nslookup' or 'host' queries via the command line,... (2 Replies)
Discussion started by: saabir
2 Replies

2. Shell Programming and Scripting

Frustrating Disk space script

This my frustrating disk space script that is supposed to send me a email whenever the disk space reaches 90% but this has some problem that just would not work ..can anyone please tell me when im going wrong #!/bin/ksh sendemail=-1 space=`df -bhk /users/siebelserver |awk '{print$5}'` echo... (4 Replies)
Discussion started by: vivsiv
4 Replies

3. AIX

Where are my groups

Hello A couple of weeks ago, I added a user to an AIX 5.3 system. I go to add one today, and it appears that when creating a user in smit, I cannot see any groups. No primary groups No Group set No Admin Groups The /etc/group and etc/secuity/group files seem to be intact. I did... (4 Replies)
Discussion started by: mhenryj
4 Replies

4. Solaris

groups

how to create 1000 users in 1 group (0 Replies)
Discussion started by: tirupathi
0 Replies

5. Solaris

groups

1 user in member of 4 groups find file permissions and default group (1 Reply)
Discussion started by: tirupathi
1 Replies

6. UNIX for Dummies Questions & Answers

Frustrating but simple preference question

So I am set up on a new box for work here and I have a frustrating preference issue. Whenever I hit backspace, it deletes a whole word instead of a single character. I understand that this is generally the functionality of hitting ctrl-backspace. I tried googling for a solution and dabbled... (3 Replies)
Discussion started by: jasondj
3 Replies

7. UNIX for Dummies Questions & Answers

Groups

Must I be in a group? I am using Ubuntu and am the only user on my PC. I know how to change groups but do not see a way to not be in a group. Any help would be appreciated. (2 Replies)
Discussion started by: nthepines
2 Replies

8. Shell Programming and Scripting

Frustrating error special character <96>

Hiya Folks, Wondering if anybody has ran into this before, it's driving me nuts! Searching on this in the forums didn't turn up anything that was any help. My script is going through a csv file I have, running ksh under Cygwin. The code I have is... REQUEST_TYPE=$(grep REQ $FILES |... (3 Replies)
Discussion started by: jtollefson
3 Replies

9. Ubuntu

PPPOE + Ubuntu = Frustrating

Hii everyone, I will be explaining what kind of problem I am having with Ubuntu and PPPOE. I have dual booted my PC with Win 7 and Ubuntu 10.10 Previously, whenever I use to start my ubuntu, internet automatically used to start up.. .no problems. I had created a DSL connection through... (0 Replies)
Discussion started by: zsycho
0 Replies

10. Shell Programming and Scripting

Frustrating in splitting text files

Duplicate threads merged Dear all, I have been working with a very large text file manually. I'm ordering how to do this with a script. The gamma should be straightforward: I just want split the text into multiple files. The file name should be "CP1", "TS1 for the second step", "PR1 for... (3 Replies)
Discussion started by: liuzhencc
3 Replies
IO::CaptureOutput(3pm)					User Contributed Perl Documentation				    IO::CaptureOutput(3pm)

NAME
IO::CaptureOutput - capture STDOUT and STDERR from Perl code, subprocesses or XS VERSION
This documentation describes version 1.1102. SYNOPSIS
use IO::CaptureOutput qw(capture qxx qxy); # STDOUT and STDERR separately capture { noisy_sub(@args) } $stdout, $stderr; # STDOUT and STDERR together capture { noisy_sub(@args) } $combined, $combined; # STDOUT and STDERR from external command ($stdout, $stderr, $success) = qxx( @cmd ); # STDOUT and STDERR together from external command ($combined, $success) = qxy( @cmd ); DESCRIPTION
This module provides routines for capturing STDOUT and STDERR from perl subroutines, forked system calls (e.g. "system()", "fork()") and from XS or C modules. FUNCTIONS
The following functions will be exported on demand. capture() capture &subroutine, $stdout, $stderr; Captures everything printed to "STDOUT" and "STDERR" for the duration of &subroutine. $stdout and $stderr are optional scalars that will contain "STDOUT" and "STDERR" respectively. "capture()" uses a code prototype so the first argument can be specified directly within brackets if desired. # shorthand with prototype capture { print __PACKAGE__ } $stdout, $stderr; Returns the return value(s) of &subroutine. The sub is called in the same context as "capture()" was called e.g.: @rv = capture { wantarray } ; # returns true $rv = capture { wantarray } ; # returns defined, but not true capture { wantarray }; # void, returns undef "capture()" is able to capture output from subprocesses and C code, which traditional "tie()" methods of output capture are unable to do. Note: "capture()" will only capture output that has been written or flushed to the filehandle. If the two scalar references refer to the same scalar, then "STDERR" will be merged to "STDOUT" before capturing and the scalar will hold the combined output of both. capture &subroutine, $combined, $combined; Normally, "capture()" uses anonymous, temporary files for capturing output. If desired, specific file names may be provided instead as additional options. capture &subroutine, $stdout, $stderr, $out_file, $err_file; Files provided will be clobbered, overwriting any previous data, but will persist after the call to "capture()" for inspection or other manipulation. By default, when no references are provided to hold STDOUT or STDERR, output is captured and silently discarded. # Capture STDOUT, discard STDERR capture &subroutine, $stdout; # Discard STDOUT, capture STDERR capture &subroutine, undef, $stderr; However, even when using "undef", output can be captured to specific files. # Capture STDOUT to a specific file, discard STDERR capture &subroutine, $stdout, undef, $outfile; # Discard STDOUT, capture STDERR to a specific file capture &subroutine, undef, $stderr, undef, $err_file; # Discard both, capture merged output to a specific file capture &subroutine, undef, undef, $mergedfile; It is a fatal error to merge STDOUT and STDERR and request separate, specific files for capture. # ERROR: capture &subroutine, $stdout, $stdout, $out_file, $err_file; capture &subroutine, undef, undef, $out_file, $err_file; If either STDOUT or STDERR should be passed through to the terminal instead of captured, provide a reference to undef -- "undef" -- instead of a capture variable. # Capture STDOUT, display STDERR capture &subroutine, $stdout, undef; # Display STDOUT, capture STDERR capture &subroutine, undef, $stderr; capture_exec() ($stdout, $stderr, $success, $exit_code) = capture_exec(@args); Captures and returns the output from "system(@args)". In scalar context, "capture_exec()" will return what was printed to "STDOUT". In list context, it returns what was printed to "STDOUT" and "STDERR" as well as a success flag and the exit value. $stdout = capture_exec('perl', '-e', 'print "hello world"'); ($stdout, $stderr, $success, $exit_code) = capture_exec('perl', '-e', 'warn "Test"'); "capture_exec" passes its arguments to "system()" and on MSWin32 will protect arguments with shell quotes if necessary. This makes it a handy and slightly more portable alternative to backticks, piped "open()" and "IPC::Open3". The $success flag returned will be true if the command ran successfully and false if it did not (if the command could not be run or if it ran and returned a non-zero exit value). On failure, the raw exit value of the "system()" call is available both in the $exit_code returned and in the $? variable. ($stdout, $stderr, $success, $exit_code) = capture_exec('perl', '-e', 'warn "Test" and exit 1'); if ( ! $success ) { print "The exit code was " . ($exit_code >> 8) . " "; } See perlvar for more information on interpreting a child process exit code. capture_exec_combined() ($combined, $success, $exit_code) = capture_exec_combined( 'perl', '-e', 'print "hello "', 'warn "Test " ); This is just like "capture_exec()", except that it merges "STDERR" with "STDOUT" before capturing output. Note: there is no guarantee that text printed to "STDOUT" and "STDERR" in the subprocess will be appear in order. The actual order will depend on how IO buffering is handled in the subprocess. qxx() This is an alias for "capture_exec()". qxy() This is an alias for "capture_exec_combined()". SEE ALSO
o IPC::Open3 o IO::Capture o IO::Utils o IPC::System::Simple AUTHORS
o Simon Flack <simonflk _AT_ cpan.org> (original author) o David Golden <dagolden _AT_ cpan.org> (co-maintainer since version 1.04) COPYRIGHT AND LICENSE
Portions copyright 2004, 2005 Simon Flack. Portions copyright 2007, 2008 David Golden. All rights reserved. You may distribute under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file. perl v5.10.1 2010-02-15 IO::CaptureOutput(3pm)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy