Quote:
Originally Posted by
c3rb3rus
I did notice the dependency hell on perilz which prevented me from getting Samba installed on the AIX OS, I was finding that it needed dependency A which needed dependency B, and so on the chain was huge.
Michael Perzl is probably the most structured worker i ever came across. Yes, that means that "packageA" really contains only A and not a iota of B, which might create a dependency to B, but you will come to appreciate the robustness and dependability his packages offer. Something unexpected practically never happens. This is arguably the best site for third-party AIX software and the packages are way better than the rpm-packages IBM itself offers.
Quote:
Originally Posted by
c3rb3rus
I was also succesful at removing Samba, however I did notice that using..
lssrc -g Samba config. remained behind, showing the samba group (nmbd, winbindd, and smbd services). perhaps the previous admin manually created the service group thus the removal did not take care of it.
hmm....
"lssrc" ist listing
running ("active") and
stopped ("inoperative") subsystems (~=daemons), not files. It is the interface to the "System Resource Controller" (SRC), a sort-of super-daemon. You will find some information here if you search for it.
It might well be that the previous admin created some users/groups himself. There are some easy commands to find out what belongs to where:
"lslpp -l" lists all installed packages in a long list
"lslpp -f <package-name>" lists all the files/directories belonging to the package
"lslpp -w <file>" lists the package a file belongs to (if any)
You can even "take apart" lpp-packages and look into their pre-/post-install-scripts, which would be responsible for creating users, groups and the like.
I hope this helps.
bakunin