You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org> on 2012/02/07 20:40:59 UTC
[jira] [Commented] (WHIRR-501) Disable Crond before bootstrap and
re-enable after configuration
[ https://issues.apache.org/jira/browse/WHIRR-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202678#comment-13202678 ]
Andrei Savu commented on WHIRR-501:
-----------------------------------
Note: it may not work if by the time we stop crond apt-get is already running a long task (like upgrade). Would it be a better idea to have a function like apt-get-install-with-try in whirr core?
> Disable Crond before bootstrap and re-enable after configuration
> ----------------------------------------------------------------
>
> Key: WHIRR-501
> URL: https://issues.apache.org/jira/browse/WHIRR-501
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.5.0, 0.6.0, 0.7.0
> Reporter: Andrei Savu
> Fix For: 0.8.0
>
>
> This problem was identified by Karel and I think the easiest workaround we can implement is to stop the crond service before bootstrap and start it again after configuration.
> Relevant info here: http://www.cyberciti.biz/faq/howto-linux-unix-start-restart-cron/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira