On 8/5/2013 5:26 AM, Anton Aylward wrote:
Similarly unless there are other specific entries, systemd supports, in its backward compatibility mode, entries from /etc/init.d that haven't been converted. This is what you are seeing. I'm sure Cristian can explain better. And yes its documented. ... There isn't a specific smb unit, its part of the automatic generation of entries (that remain to be converted) of /etc/init.d entries which I mentioned above.
systemctl -a| grep smb
However it does give you enough information to create a a custom smb.service unit of your own in /etc/systemd/
Its not difficult and its not scary. You have plenty of other examples to show you how its done.
So is this the plan for the foreseeable future, or merely a kludge for the present so as to not to have to totally rebuild OpenSuse and Yast? Is auto-generation a sustainable mechanize? Then, circling around to the original problem, that if smb or nmb failing to start, does it make more sense to set up one's own smb.service than to fix the problem in the auto generation engine? It would seem that if opensuse is going to continue to use auto generation that the wisest fix would be to fix that, rather than end-running the entire process. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org