Custom Query (894 matches)
Results (112 - 114 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #1024 | desai | https://www.google.com/accounts/o8/id?id=AItOawkPb0RtPyicSdU7pLcv1UrX-yCh-YjkOwU | fixed | Broken link to Magic Groups |
| Description |
http://docs.bcfg2.org/quickstart/ubuntu.html Link to Magic Groups on this wiki is broken. |
|||
| #983 | rcuza | rcuza | fixed | Build Failing For osx Package |
| Description |
While trying to build the bcfg2 package for OS X I ran into the following error: chown: $PATH/$FILE: Operation not permitted A workaround is to run make as root (sudo make), but this is not desirable if it can be avoided. To reproduce this error run the following: $ git clone git://git.mcs.anl.gov/bcfg2.git $ git checkout v1.1.1 $ make More detailed snippet of error log: running install_egg_info Writing osx/bcfg2pkg/Library/Python/2.6/site-packages/Bcfg2-1.1.1-py2.6.egg-info /usr/sbin/chown -R root:admin "bcfg2pkg" chown: bcfg2pkg/Library/Frameworks/Python.framework/Versions/Current/share/bcfg2/Hostbase/repo/batchadd.tmpl: Operation not permitted chown: bcfg2pkg/Library/Frameworks/Python.framework/Versions/Current/share/bcfg2/Hostbase/repo/dhcpd.conf.head: Operation not permitted chown: bcfg2pkg/Library/Frameworks/Python.framework/Versions/Current/share/bcfg2/Hostbase/repo/dhcpd.tmpl: Operation not permitted I've attached the full output of make to this ticket. |
|||
| #434 | desai | jacques | fixed | Build mode not working. services still restarted. |
| Description |
When I use the -B option, the services are still started/restarted in 0.9.3pre6. I am pretty sure it comes from bcfg2 rather that apt-get/dpkg (debian) since I see /etc/init.d/??? calls in the -d output but in any case, it does break my systemimager setup. The work around that I am using (it could be reused if the problem comes from dpkg) is to create a fake /usr/sbin/invoke-rc.d and /sbin/start-stop-daemon with dpkg-divert'ing all the modifications to a renamed version. This way no process are restarted and no filesystem ends up un-umountable. That is obviously a plugin specific issue, but I also think that the bcfg2 should apply the package policy there, that is, not to call /etc/init.d directly but through the invoke-rc.d hook. One does not know what kind of magic may be plugged in that file on some systems and bcfg2-client can be pretty close to apt-get/dpkg in terms of end effects on the os. Feel free to disagree, but still... jacques |
|||
