A bug that has caused some tty12 problems for some people has been fixed and an expansion to the 66-tree tool is also coming on this next release.
A new option on 66-tree that allows you to order which
tree starts after which tree with configurant -S (starts after)
It may not seem as important yet but some admins are evolving together with 66 demanding more complicated service structures. As you saw in the 0.2.4 edition the significant change was how one service may depend on the pre-existing running of another service. Now you can have whole trees of services requiring another tree to be active already, It is hard to give an example with services that don't require such functionality, but let's say you have a networking tree and without it you have no network access, and a file server tree. For the file server tree to be activated (66-all) the networking tree must already be active. So by creating or modifying such a fileserver tree you can use the option -S and specify the tree that must also be activated before this one becomes active. You can have services struggle with each other and produce unnecessary logging events (..trying to bring apache up but there is no net. access ..) but now there is a way to have a cleaner more efficient system that doesn't produce unnecessary "trash".
Just when you thought you have seen it all :)
TheObarunTeam
A new option on 66-tree that allows you to order which
tree starts after which tree with configurant -S (starts after)
It may not seem as important yet but some admins are evolving together with 66 demanding more complicated service structures. As you saw in the 0.2.4 edition the significant change was how one service may depend on the pre-existing running of another service. Now you can have whole trees of services requiring another tree to be active already, It is hard to give an example with services that don't require such functionality, but let's say you have a networking tree and without it you have no network access, and a file server tree. For the file server tree to be activated (66-all) the networking tree must already be active. So by creating or modifying such a fileserver tree you can use the option -S and specify the tree that must also be activated before this one becomes active. You can have services struggle with each other and produce unnecessary logging events (..trying to bring apache up but there is no net. access ..) but now there is a way to have a cleaner more efficient system that doesn't produce unnecessary "trash".
Just when you thought you have seen it all :)
TheObarunTeam
