First of all, you don't really need the output.txt file, you can redirect the output of your command to the perl script as in $ sudo dscl . list groups gid | program.pl and read the data from stdin (while(<>)) without the need of open and close.
To parse the lines you can use a regex match like this> $_ =~ /^\s*(\S+)\s*(\d+)\s*$/; if the line matches, you'll find the group name in $1 and the ID in $2.
Updated: corrected a type in the first code line. Thanks to toolic and, no, I don't know if mac is very different from unix, but this keyboard I'm using today is very different from my own! :-)
Rule One: "Do not act incautiously when confronting a little bald wrinkly smiling man."
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.