On Thu, 03 Mar 2011 23:59:47 -0800, petermity <6t12-n6js(a)dea.spamcon.org> wrote:
Yes, I saw that in my tests today.
I would still like to be able to check if a snippets file exists.
File a bug on this in trac and I'll see if there is a good way to do this.
Alternately, have some way to choose, individually for each snippet,
the
behavior of Cobbler when it encounters a missing snippet.
One way or another, if a snippet that is critical to my kickstart
expectations doesn't exist, I would like Cobbler (getks/validateks) to
abort with an error (see recent thread "How to force failure").
If a snippet is not critical, I would like Cobbler to say nothing, so that
there are no extraneous "Error" messages when checking getks output.
There should be no error messages because it outputs a comment.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME