-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael DeHaan wrote: >> If you're just using "command", then yes, we do need some form of raw >> output mode, even if it's just as simple as > >> system X: >> output here > >> system Y: >> output here In my biased opinion that makes perfect sense and thats really the basic level I'd be looking for, even if the output is only formated in this manner when using the command function. > >> And that should probably be the default. The thing is, in the case of >> yum update, you really only need to know what >> succeeds or fails, so you need even less than that. So func just gives >> you return codes. >> Are you saying you want the full output for each system or better >> formatted return codes? > >> We're really not trying to match up the output for SSH against one >> system because it's not always going to be run against one system, >> though I can see in some cases it may be used against just a handful. > >> There's an interesting line to walk between concentrating on the >> scripting cases and "for humans" usage. I think the primary focus of >> Func is clearly on the former, but we need the command line to be >> workable too for people who are testing things out. Yep. The entire discussion revolves around intended audience. - -- # Paul Lundin # plundin@xxxxxxxxxx # GPG key: 2DE452BE # Senior Systems Administrator # Red Hat inc http://www.redhat.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFIMtDm6KVQKC3kUr4RAkiWAJ9enkYZYwr+G5x0gZUprFuzlx8HdgCeIqbR rNvPJPGGMa+0lQ3v7eMLgOI= =gr5w -----END PGP SIGNATURE----- _______________________________________________ Func-list mailing list Func-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/func-list
