SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
An idea for Winbind users.
Personally I use winbind, for Single sign on(with Kerberos) and to take a unique uid unique for all users (winbind+samba+idmap by ldap server). Is nice because user has the same uid on all systems(Linux,Hp-ux,AIX,etc..).
The original script of rc.samba doesn't include winbindd. I have a dirty solution adding Winbindd after smbd and nmbd daemons in the rc.samba script, a better solution would be a script which start Winbindd if needed, or a separate rc.winbind script.
Last edited by camerabambai; 05-21-2020 at 02:10 AM.
Absolutely. Ideally, It would be great to get rid of "bin" package. Besides "tempfile" I don't remeber that I ever needed it.
Never had to use fromdos (or todos) to get rid of MS-Dos/Windows line endings?
I don't, but then again I got my own "undos" tools (NOT free) to do this:
Quote:
undos,tounix,todos,tocpm,tomac,unmac,unparity ‐ Change ASCII file format for target operating system
Undos and tounix convert DOS or CP/M format source files to Unix format by deleting carriage returns preceding linefeeds and eliminating characters starting with CPMEOF (^Z).
Todos converts Unix format source files to DOS format by adding a carriage return (if not already present) before each linefeed, and eliminates characters starting with CPMEOF (^Z). Tocpm additionally appends CPMEOF (^Z) characters to the resulting file to make the file length a multiple of the 128 byte CP/M record length.
Any combination of undos, todos, or tocpm (without flags) may be applied to a proper ASCII file without destroying information. Lone carriage returns used to force overprinting are not translated to CR/LF pairs.
This is actaully a single executable file with hard links for the other commands and unlike the fromdos/todos pair can take multiple file arguments.
Never had to use fromdos (or todos) to get rid of MS-Dos/Windows line endings?
I don't, but then again I got my own "undos" tools (NOT free) to do this:
This is actaully a single executable file with hard links for the other commands and unlike the fromdos/todos pair can take multiple file arguments.
I used them only in Cygwin. Plain "sed" or "tr" can substitute these commands. Anyways, I agree that todos/fromdos may be needed, but as separate package. Currently, "bin" contains things from 5 different sources (todos, fbset, debianutils, xx, diskcopy). It's not just "bin", it's a "garbage-bin" I'm pretty sure that most of those things are not relevant anymore, like tempfile from debianutils.
The original script of rc.samba doesn't include winbindd. I have a dirty solution adding Winbindd after smbd and nmbd daemons in the rc.samba script, a better solution would be a script which start Winbindd if needed, or a separate rc.winbind script.
It's actually worse than that, as Samba needs to be started/stopped in 3 different ways, depending on how Samba is configured:
If samba is a standalone server, smbd and nmbd should be started in that order; stopping samba can be accomplished by simply killing the processes
If samba is a domain member, smbd, nmbd, and winbindd should be started in that order; as in the above case, a simple kill is all that's needed to stop samba
If samba is an AD Domain Controller, the samba executable/process is the only component that should be started/killed; the individual daemons should never be manually invoked or stopped
The only reliable way to determine which role samba is configured as, is to parse the output of testparm. I use a modified rc.samba that takes all this into account.
The only reliable way to determine which role samba is configured as, is to parse the output of testparm. I use a modified rc.samba that takes all this into account.
Do you have an example you'd be willing to share? It might be something that Pat will add to the distro.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I'm pretty sure that most of those things are not relevant anymore, like tempfile from debianutils.
