How would you use chkconfig to all bigd from all runlevels?

How would you use chkconfig to remove bigd from all runlevels?

chkconfig --del bigd

How would you use chkconfig to set the bigd daemon to start at runlevels 2 and 3?

Firstly, your script to control the bigd daemon must be written with specific reference to chkconfig. If you look at other scripts in /etc/init.d you will see many that follow a similar format to this (this is from the script /etc/rc.d/init.d/sshd):- #!/bin/bash # # Init file for OpenSSH server daemon # # chkconfig: 2345 55 25 # description: OpenSSH server daemon The three "numbers" following "chkconfig:" determine how chkconfig will add the script to the startup and shutdown events. The first number is actually a list of run-levels that the script should be started in. In this case, the sshd daemon will be started in run-levels 2, 3, 4 and 5. Ergo, in run-levels 0, 1 and 6 the sshd daemon will be stopped or killed. The second and third numbers control the order in which the process is started (55) and killed (25). A look a the list of entries in the rc.d directory for sshd should help explain this:- /etc/rc.d/init.d/sshd /etc/rc.d/rc0.d/K25sshd /etc/rc.d/rc1.d/K25sshd /etc/rc.d/rc2.d/S55sshd /etc/rc.d/rc3.d/S55sshd /etc/rc.d/rc4.d/S55sshd /etc/rc.d/rc5.d/S55sshd /etc/rc.d/rc6.d/K25sshd Each of the entries in the rcN.d (where N = 0 to 6) directories is a symbolic link back to the base script in /etc/rc.d/init.d/sshd. So when run-level 2 is initiated, /etc/rc.d/rc2.d/S55sshd is run. There are many other links in the /etc/rc.d/rc2.d to other scripts in /etc/rc.d/init.d, and the prefix added by chkconfig (i.e. S55 in the case of sshd) determines the sequence in which these scripts are performed. So sshd is started in run-level 2 after all the "earlier" entries have already been started (e.g. scripts starting with S10, S20, S30 etc.). For custom scripts, you would be advised to use a high number to start the script (e.g. 99) and a low number to stop/kill it. This will ensure all dependent processes are started when you start your script. To conclude, your bigd script should have something like this at the top of the file:- #!/bin/bash # # Init file for BIG server daemon # # chkconfig: 23 99 00 # description: Script to start bigd Then you can use "chkconfig --add bigd" to create all the symbolic links in the appropriate /etc/rcN.d directories. I hope that helps :)

What command is used to see a list of all services currently installed?

chkconfig --list

What script contains the default runlevels?

The default runlevel is specified in /etc/inittab. There is no universally accepted runlevel that is specified as the "default." Red Hat and Fedora use 3 or 5, Ubuntu uses 2, Mandriva and SUSE use 5, and Gentoo uses 3. Some (a relatively small number) Linux distros do not use a SysV init style, and thus have no runlevels at all.

What would happen if all plants if all plants had the same kind of roots?

they would all look the same

Where would you be without machines?

all of our all clothes would be very dirty (ALL THE TIME)

Why you need to be creative?

If nobody was creative, then we would all be the same. If we were all the same, then we would all have the same ideas. If that were true, then nothing would ever get done. If nothing ever changed, then we would all die.

How do you join a Linux computer to a domain group?

First, make sure kerberos is installed: # rpm -qa | grep krb this should return at least 3 packages: krb5-devel, krb5-libs and krb5-workstation Next, make sure the ldap development libraries are installed: # rpm -qa | grep ldap-devel If either of these returns nothing, you'll need to install them - which you can do from the Redhat CD. make sure there's an entry for your active directory DC in your /etc/hosts file: 1.2.3.4 addc.example.com addc Next, edit your /etc/krb5.conf to match your site. Everything should be fairly self-explanitory - and everything is case sensitive. Do not comment this file. Once you've gotten to this point, you can try: # /usr/kerberos/bin/kinit user@DOMAIN.COM replacing *user* with a real user and DOMAIN.COM with a real domain (which must be UPPERCASE). If things are working, you'll be prompted for a password. If you enter the correct password, you'll come back to a bash shell, if not, you should be presented with: "kinit(v5): Preauthentication failed while getting initial credentials" or some such. Note: If the clock time on the Linux machine is more than 5 minutes off from the time on the windows machine no ticket information will work. There are three wys to deal with this: 1. Have the Linux server act as a network time server, with the windows machine as a client 2. Have the windows machine act as a time server for the Linux client 3. Make both systems pull the time from the same 3rd server ( some are listed here - http://ntp.isc.org/bin/view/Servers/NTPPoolServers ) Next, uninstall samba if it's installed: # rpm -e samba get the latest version of samba: $ wget "http://us1.samba.org/samba/ftp/samba-latest.tar.gz" things to do { 01.$ tar -zxvf samba*.tar.gz 02. 03.$ CD samba-3.0.13 04. 05.$ ./configure --prefix=/usr/local/samba --with-ldap --with-ads --with-krb5 --with-pam --with-winbind 06. 07.# make && make install } In your smb.conf: netbios name = LINUX_SERVER_NAME realm = DOMAIN.COM ads server = 123.123.123.123 security = ADS encrypt passwords = yes start samba: # /etc/RC.d/init.d/smb start To add the Linux computer to the AD, you need to log into the DC and add it as a user with such privledges, so (from the Linux system): # /usr/local/samba/bin/net ads join -U Administrator it should prompt you for Administrator's password. Note that Administrator should be a user with the right to add a computer to the AD. you should see something like: Joined 'LINUX_MACHINE_NAME' to realm 'DOMAIN.COM' To verify this worked, go to the windows DC and open Active Directory->Users and Computers and look for your Linux machine to be listed there. That's all you absolutely need to connect to the AD. If you want to map users to the AD (which is probably why you're doing this), open /etc/nsswitch.conf and change this: passwd: files shadow: files group: files to this: passwd: compat winbind shadow: compat group: compat winbind start the winbind daemon: # winbindd make sure it's running: # PS -ae | grep winbindd if nothing gets returned, you probably didn't configure samba with kerberos and ldap support. If it shows winbindd running, you're all set. To make sure everything starts on reboot: open /etc/RC.d/init.d/smb and /etc/RC.d/init.d/winbindd and make sure the line: # chkconfig: 345 NN NN exixts (NN will be different numbers pertaining to priority), it should be on line 3 of both files. if these lines don't exist, add them. If they read: # chkconfig: - NN NN change the - to 345 save and close those files and run chkconfig: # chkconfig smb reset # chkconfig winbindd reset you can check the runlevels they will start at with # chkconfig smb --list # chkconfig winbindd --list in your smb.conf [global] section: (for name resolution) Code: wins support = Yes name resolve order = wins lmhosts hosts bcast wins server = wins_server_ip_address 01. wins support = Yes 02. name resolve order = wins lmhosts hosts bcast 03. wins server = wins_server_ip_address

Do you take a gift to an ordination?

no!not at all that would be crazy! no!not at all that would be crazy!

Why are prisms and pyramids different?

If they were not different they would all be called the same thing!If they were not different they would all be called the same thing!If they were not different they would all be called the same thing!If they were not different they would all be called the same thing!

What would earth do without the sun?

We would all freeze because there was no light, therefore, we would all die.

What would happen if nobody ate anything?

We would all starve and die off.