0
Add your answer:
Earn +20 pts
How would you use chkconfig to remove bigd from all runlevels?
chkconfig --del bigd
How would you use chkconfig to all bigd from all runlevels?
chkconfig --del bigd
How would you use the service command to manually kill the bigd daemon?
Service bigd stop
What would you name the link to kill the fictitious bigd daemon?
Kill -9
What would you name the link to an init script that would start the fictitious bigd demon early in the boot process?
Kill -9
What would you name the link to an init script that would kill the fictitious bigd daemon early in the boot process?
/etc/rc5.bigd.d
What would you name the link to an init script what would start the fictitious bigd daemon early in the boots process?
/etc/rc5.bigd.d
What would you name the link to an init script that would start the fictitious bigd daemon early in the boot process in Fedora Linux?
/etc/rc5.bigd.d
What actors and actresses appeared in Valentine Crush - 2014?
The cast of Valentine Crush - 2014 includes: Damien Augustus as Rodger Holly Haith as Patty Jeremy Kirby as Doug Bigd
What would you name the link to an init script that would start the fictitious bigd daemon early in the boot process and what would you name the link to kill the same daemon?
/etc/rc5.bigd.dDoes someone copy some of these questions out of on-line tests or quizes? They seem too well written and too easy to answer to be real user questions.
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 :)
How do you block other websites from using your files?
The method one might use to prevent other websites operating on different servers from obtaining content from your website would be decided largely by two variables: First, the server your website is operating on, and second, the type of file you want to permit from being accessed from other servers. Say your site is running Apache, and theres a good chance it is, you would use a .htaccess file and store it in your sites root directory. In that file, you would specify the following: which servers you wanted to block (or all of them), which you wanted to allow (if any), which file types you don't want available to these blocked sites, and finally - you might define a special web page users on the foreign site will see when they try to access the protected file on your site. To learn how to do this, simply preform a Google search like "block other servers from accessing gif files on apache". Hope this helps! -bigd
