Yes, my cobbler log contains some helpful info, but how to bring this
excerpt to the UI if we are only reacting to a download that failed? I
didn't dig deep into it, I just wanted to hide the html source of the 500
error page. But I agree it would be much better to present such details to
the
Hello,
When scheduling many repo syncs at a time (as 'mgr-ncc-sync' does it), we
experienced
that not all of the channels were actually getting a refresh, try it with e.g.
~ 30.
After some research we found that this is due to the 'repeat count' parameter
given to
the SimpleTrigger constructor
On 11/12/2012 01:31 PM, Tomas Lestach wrote:
Yes, my cobbler log contains some helpful info, but how to bring this
excerpt to the UI if we are only reacting to a download that failed? I
didn't dig deep into it, I just wanted to hide the html source of the 500
error page. But I agree it would
Thank you, I merged your commits into our branch, but did not do any testing
yet. Two remarks regarding d1789a9e:
- I fixed a typo in one of the new messages: bellow - below
- I think we could omit the ';' after the '}' of the newly inserted css
A patch is attached.
Applied as:
