On 29/02/12 12:28, Robert Jacobson wrote:
On 2/29/2012 2:12 AM, André Gemünd wrote:
I'm not sure I understand the question right, but the kickstart file is generated ad-hoc on access through the HTTP server. You can view the output through
cobbler system getks --name=YourSystem
The templates lie in /var/lib/cobbler/kickstarts
Greetings André
Thanks.
I think my problem was -- I didn't realize before that the kickstart was being generated dynamically. I was looking for a file on the system "systemname" because that's what the browser displayed in the URL. But I now realize there is no such file.
What I should have been doing is looking at the profile and seeing what template it was based on (in this case it was "sample.ks"). "sample.ks" is full of snippets, so it doesn't really look like the final kickstart file presented to the client. i.e. The final kickstart file is dynamically generated and doesn't exist anywhere on the system.
Another "gotcha" I found, related to the parsing error I was seeing. It seems that the output of the snippets (generated by Cheetah?) can contain $() clauses, but the Cheetah parser will not accept $() as input without escaping the dollar($) with a backslash ().
Indeed. The kickstart templates are evaluated by cheetah, which attempts to substitute variables for just about anything it sees beginning with a '$' symbol, unless it's marked as raw text, or part of a cheetah instruction. Some things definitely trip it up. The $() construct is one of them.
more info here: https://github.com/cobbler/cobbler/wiki/kickstart%20templating
The Cheetah user guide is also handy for language docs http://packages.python.org/Cheetah/users_guide/language.html
Stuart