Sponsored Content
Operating Systems Linux SuSE Setting up Suse 11.0 as server Post 302300411 by woofie on Tuesday 24th of March 2009 05:51:07 AM
Old 03-24-2009
Thanks for the reply.

I got no problem with SUSE and the graphics I got a machine given to me and it's got enough specs to run it.

Thought I was going down the right track with Samba, OpenLDAP but didn't know about Kerberos. I installed all the server features on the machine so I can play around and test the settings.

For the mail I want to have it (sorry I didn't say more clearly). To get mail from (for now) my ISP and then when I log into the network from another computer I can get the mail.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

suse server 8.0 on hp server problem

machine: Hp Proliant DL145/Opterom 2.4GH 2*72 GBB SCSi hdd, suse: suse linux Enterprose server 8.0 for Amd 64 problem: 1. can not boot properly. have to use installation disk to boot it: enter installation and choose "boot from existing installation" and this is the only option. ( just... (1 Reply)
Discussion started by: murataht
1 Replies

2. Filesystems, Disks and Memory

Problem setting up raw partitions on SUSE v8.0 using LVM on Oracle 8.1.7.URGENT!!!!!!

Hi all! Working on Oracle v8.1.7.0.0 with OS  as Suse v8.0 Linux. I had created LVM,linked raw devices to LVM as below: # for binding raw devices raw /dev/raw/raw1 /dev/oracle/sam_raw_system_251m raw /dev/raw/raw2 /dev/oracle/sam_raw_users_26m raw /dev/raw/raw3... (2 Replies)
Discussion started by: Amitstora
2 Replies

3. SuSE

LKCD for suse linux enterprise server 8

Hi, I have installed LKCD using lkcdutils pakage through Yast install and remove applications. I have used enterprise server cd for installation. But I did not found any service of lkcd like /etc/init.d/boo.lkcd there. if we dont have this servers lkcd dump can not be saved at dump... (0 Replies)
Discussion started by: bryanabhay
0 Replies

4. SuSE

Extend root partition on SuSE enterprise Server 11.1

Hello Folks, Greetings, I am in need of extending the / partition for one of my SuSE linux Enterprise Server 11.1 which is running on VMware. I will be able to extend the virtual lun from the vshphere console but not sure how to extend the root partition from the OS end. I am not sure if I... (1 Reply)
Discussion started by: PSP
1 Replies

5. UNIX for Dummies Questions & Answers

Help with printing to a print server from Suse 11

All; I really have 2 questions 1) How can I tell what filter file is attached to a printer ? 2) Is ther an easy way to script a socket (port9100) command to send print files to the print server? Thank you (0 Replies)
Discussion started by: Hughie
0 Replies

6. SuSE

Hot-add memory to SuSE / VMware virtual server

Hi, Here is the issue. Some more memory has been added from vCenter to the virtual machine. From the virtual machine running SuSE 11 SP3. # modprobe acpiphp # modprobe acpi-memhotplug # grep -v online /sys/devices/system/memory/*/state # It looks like there is no offline memory, but free... (1 Reply)
Discussion started by: aixlover
1 Replies

7. SuSE

How to find Server model in Suse?

How to find Server model in Suse? dmidecode is not working here server gives output for hwinfo, but not listing lshw,lshal etc. Server is remotely located, so I cant find it physically. dmesg command is also not helping with boot logs. I am not a Suse admin, request fast reply. Thanks Shyam (6 Replies)
Discussion started by: shyam2j
6 Replies

8. SuSE

Suse enterprise server installation help

hello All, good day to you. could you tell me is there any way I can download SUSE lunux enterprise server trail version ? I want to install sap application over it. thanks in advance. (1 Reply)
Discussion started by: Leaner_963
1 Replies
REALMD.CONF(5)							   File Formats 						    REALMD.CONF(5)

NAME
realmd.conf - Tweak behavior of realmd CONFIGURATION FILE
realmd can be tweaked by network administrators to act in specific ways. This is done by placing settings in a /etc/realmd.conf. This file does not exist by default. The syntax of this file is the same as an INI file or Desktop Entry file. In general, settings in this file only apply at the point of joining a domain or realm. Once the realm has been setup the settings have no effect. You may choose to configure SSSD[1] or Winbind[2] directly. Only specify the settings you wish to override in the /etc/realmd.conf file. Settings not specified will be loaded from their packaged defaults. Only override the settings below. You may find other settings if you look through the realmd source code. However these are not guaranteed to remain stable. There are various sections in the config file. Some sections are global topic sections, and are listed below. Other sections are specific to a given realm. These realm specific sections should always contain the domain name in lower case as their section header. Examples of each setting is found below, including the header of the section it should be placed in. However in the resulting file only include each section once, and combine the various section setting together as lines underneath the section. For example [users] default-home = /home/%U default-shell = /bin/bash ACTIVE-DIRECTORY These options should go in an [active-directory] section of the /etc/realmd.conf file. Only specify the settings you wish to override. default-client Specify the default-client setting in order to control which client software is the preferred default for use with Active Directory. [active-directory] default-client = sssd # default-client = winbind The default setting for this is sssd which uses SSSD[1] as the Active Directory client. You can also specify winbind to use Samba Winbind[2]. Some callers of realmd such as the realm command line tool allow specifying which client software should be used. Others, such as GNOME Control Center, simplify choose the default. You can verify the preferred default client softawre by running the following command. The realm with the preferred client software will be listed first. $ realm discover domain.example.com domain.example.com configured: no server-software: active-directory client-software: sssd type: kerberos realm-name: AD.THEWALTER.LAN domain-name: ad.thewalter.lan domain.example.com configured: no server-software: active-directory client-software: winbind type: kerberos realm-name: AD.THEWALTER.LAN domain-name: ad.thewalter.lan os-name (see below) os-version Specify the os-name and/or os-version settings to control the values that are placed in the computer account operatingSystem and operatingSystemVersion attributes. This is an Active Directory specific option. [active-directory] os-name = Gentoo Linux os-version = 9.9.9.9.9 SERVICE
These options should go in an [service] section of the /etc/realmd.conf file. Only specify the settings you wish to override. automatic-install Set this to no to disable automatic installation of packages via package-kit. [service] automatic-install = no # automatic-install = yes USERS
These options should go in an [users] section of the /etc/realmd.conf file. Only specify the settings you wish to override. default-home Specify the default-home setting in order to control how to set the home directory for accounts that have no home directory explicitly set. [users] default-home = /home/%D/%U # default-home = /nfs/home/%D-%U The default setting for this is /home/%D/%U. The %D format is replaced by the domain name. The %U format is replaced by the user name. You can verify the home directory for a user by running the following command. $ getent passwd 'DOMAIN/User' DOMAINuser:*:13445:13446:Name:/home/DOMAIN/user:/bin/bash Note that in the case of IPA domains, most users already have a home directory configured in the domain. Therefore this configuration setting may rarely show through. default-shell Specify the default-shell setting in order to control how to set the Unix shell for accounts that have no shell explicitly set. [users] default-shell = /bin/bash # default-shell = /bin/sh The default setting for this is /bin/bash shell. The shell should be a valid shell if you expect the domain users be able to log in. For example it should exist in the /etc/shells file. You can verify the shell for a user by running the following command. $ getent passwd 'DOMAIN/User' DOMAINuser:*:13445:13446:Name:/home/DOMAIN/user:/bin/bash Note that in the case of IPA domains, most users already have a shell configured in the domain. Therefore this configuration setting may rarely show through. REALM SPECIFIC SETTINGS
These options should go in an section with the same name as the realm in the /etc/realmd.conf file. For example for the domain.example.com domain the section would be called [domain.example.com]. To figure out the canonical name for a realm use the realm command: $ realm discover --name DOMAIN.example.com domain.example.com ... Only specify the settings you wish to override. computer-ou Specify this option to create directory computer accounts in a location other than the default. This currently only works with Active Directory domains. [domain.example.com] computer-ou = OU=Linux Computers,DC=domain,DC=example,DC=com # computer-ou = OU=Linux Computers, Specify the OU as an LDAP DN. It can be relative to the Root DSE, or a complete LDAP DN. Obviously the OU must exist in the directory. It is also possible to use the --computer-ou argument of the realm command to create a computer account at a specific OU. user-prinicpal Set the user-prinicpal to yes to create userPrincipalName attributes for the computer account in the realm, in the form host/computer@REALM [domain.example.com] user-principal = yes automatic-id-mapping This option is on by default for Active Directory realms. Turn it off to use UID and GID information stored in the directory (as-per RFC2307) rather than automatically generating UID and GID numbers. This option only makes sense for Active Directory realms. [domain.example.com] automatic-id-mapping = no # automatic-id-mapping = yes manage-system This option is on by default. Normally joining a realm affects many aspects of the configuration and management of the system. Turning this off limits the interaction with the realm or domain to authentication and identity. [domain.example.com] manage-system = no # manage-system = yes When this option is turned on realmd defaults to using domain policy to control who can log into this machine. Further adjustments to login policy can be made with the realm permit command. fully-qualified-names This option is on by default. If turned off then realm user and group names are not qualified their name. This may cause them to conflict with local user and group names. [domain.example.com] fully-qualified-names = no # fully-qualified-names = yes AUTHOR
Stef Walter <stef@thewalter.net> Maintainer NOTES
1. SSSD https://fedorahosted.org/sssd/ 2. Winbind http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/winbind.html realmd 06/10/2014 REALMD.CONF(5)
All times are GMT -4. The time now is 10:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy