Nicholas Schuetz wrote:
Yes exactly. At first I did not run the cobbler reposync though.
1.) Create Repo with WebUI and Save.
2.) Alter Existing Profile and Try to Save.
Side Question: Why is running cobbler reposync from cron recommended?
Why not run that as part as the WebUI repo_save function? And if
running it from cron is recommended should there be a --quite flag
added to that command?
It's not run from there because you might want to make a lot of edits
and then reposync when you were done (it's slow) or need to make
changes, but there's an open Trac item
for at least creating the repo config files for reposync when the repo
is edited versus just at reposync time.
Running on cron is fine, you could redirect stdout if you wanted, I
suppose, so you didn't get the email. You would want to know about
error conditions though and still get a report if there were any. I'd
recommend something like a reposync.log file, perhaps?
--Michael
On Tue, Apr 21, 2009 at 2:15 PM, Michael DeHaan
<mdehaan(a)redhat.com> wrote:
> Nicholas Schuetz wrote:
>
>> The previous repos were created from 1.4 branch via the WebUI a month
>> or two ago. Just today I created another one using 1.6.3's WebUI.
>>
>> I was able to accomplish editing the profile using the CLI example you gave:
>>
>> cobbler profile edit --name=MYPROFILE --repos="RHEL-5-i386-TEST
>> RHEL-5-i386-THIRDPARTY"
>>
> Just to be clear before I test this ... You created a new repo via the
> web app, and then went to edit the profile in the web app to reference
> the new repo?
>
> --Michael
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler