2:12 a.m.
How can I check for the existence of a snippet file before
attempting to include it? That is, something like this:
#set $mysnippet = $mysnipdir + '/mysnipfile'
#if file_exists('$mysnippet')
$SNIPPET('$mysnippet')
#end if
11:02 a.m.
On Wed, 02 Mar 2011 00:12:20 -0800, petermity <6t12-n6js(a)dea.spamcon.org> wrote:
How can I check for the existence of a snippet file before
attempting to include it? That is, something like this:
#set $mysnippet = $mysnipdir + '/mysnipfile'
#if file_exists('$mysnippet')
$SNIPPET('$mysnippet')
#end if
I believe the snippet code will simply not do anything if the snippet
you include doesn't exist. If not, I think we should do that. Perhaps
leaving behind a '#SNIPPET foo not found'.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
1:47 a.m.
Hi Scott,
>If not, I think we should do that. Perhaps leaving behind a
'#SNIPPET foo not found'.
It already leaves this message behind in the kickstart file when the snippet is not found
(cobbler-2.0.5-1.el5);
# Error: no snippet data for foo
Regards,
Stefan
-----Oorspronkelijk bericht-----
Van: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] Namens Scott Henson
Verzonden: woensdag 2 maart 2011 18:03
Aan: petermity; cobbler(a)lists.fedorahosted.org
Onderwerp: Re: How check for existence of snippet file?
On Wed, 02 Mar 2011 00:12:20 -0800, petermity <6t12-n6js(a)dea.spamcon.org> wrote:
How can I check for the existence of a snippet file before
attempting to include it? That is, something like this:
#set $mysnippet = $mysnipdir + '/mysnipfile'
#if file_exists('$mysnippet')
$SNIPPET('$mysnippet')
#end if
I believe the snippet code will simply not do anything if the snippet
you include doesn't exist. If not, I think we should do that. Perhaps
leaving behind a '#SNIPPET foo not found'.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
Informatie van de Raad voor de rechtspraak, de rechtbanken, de gerechtshoven en de
bijzondere colleges vindt u op www.rechtspraak.nl.
1:59 a.m.
"Heijmans S (spir-it)" <Heijmans(a)rechtspraak.nl> wrote:
Hi Scott,
>>If not, I think we should do that. Perhaps leaving behind a '#SNIPPET foo not
found'.
It already leaves this message behind in the kickstart file when the snippet is not found
(cobbler-2.0.5-1.el5);
# Error: no snippet data for foo
Regards,
Stefan
Yes, I saw that in my tests today.
I would still like to be able to check if a snippets file exists.
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.
-----Oorspronkelijk bericht-----
Van: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] Namens Scott Henson
Verzonden: woensdag 2 maart 2011 18:03
Aan: petermity; cobbler(a)lists.fedorahosted.org
Onderwerp: Re: How check for existence of snippet file?
On Wed, 02 Mar 2011 00:12:20 -0800, petermity <6t12-n6js(a)dea.spamcon.org> wrote:
> How can I check for the existence of a snippet file before
> attempting to include it? That is, something like this:
>
> #set $mysnippet = $mysnipdir + '/mysnipfile'
>
> #if file_exists('$mysnippet')
> $SNIPPET('$mysnippet')
> #end if
I believe the snippet code will simply not do anything if the snippet
you include doesn't exist. If not, I think we should do that. Perhaps
leaving behind a '#SNIPPET foo not found'.
1:56 p.m.
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
2:40 a.m.
Scott Henson <shenson(a)redhat.com> wrote:
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.
After fighting the Captcha to register, I have done so -
https://fedorahosted.org/cobbler/ticket/649
> 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.
Yes, I understand, the program doesn't return an error, but the rendered
kickstart comment indicates an error that causes concern.
4805
days inactive
4820
days old
cobbler@lists.fedorahosted.org
5 comments
3 participants
participants (3)
-
Heijmans S (spir-it) -
petermity -
Scott Henson