http://www.initq.com/index.php?title=Special:NewPages&feed=atom&hideliu=&hidepatrolled=&hidebots=&hideredirs=1&limit=50&namespace=0 2012-05-20T22:08:20Z From Initq MediaWiki 1.19.0 http://www.initq.com/index.php/SMS_Email_Address_List 2012-05-17T21:53:14Z

<p>Qais: </p> <hr /> <div>This site aims to be the most complete and up to date list of email addresses that can be used to send text messages to phones. Hence email text messages or email-to-sms. This is the most simple way of sending text messages from the internet or from your computer to phones. These email addresses essentially act as a direct link to a carriers SMS gateway. Most other lists of carrier's text messaging email addresses are out of date and obsolete in 2007. The biggest change being Cingular consolidating everything to a new AT&amp;T email address for their wireless subscribers. This list can be used to help developers develop free text messaging solutions and services. The list includes US, Canadian and international mobile carriers for worldwide texting. <br /> <br /> =US &amp; Canadian Carriers=<br /> <br /> <br /> ==3 River Wireless==<br /> <br /> 10digitphonenumber@sms.3rivers.net<br /> <br /> ==ACS Wireless==<br /> <br /> 10digitphonenumber@paging.acswireless.com<br /> <br /> ==Alltel==<br /> <br /> 10digitphonenumber@message.alltel.com<br /> <br /> ==AT&amp;T==<br /> <br /> 10digitphonenumber@txt.att.net<br /> <br /> ==Bell Canada==<br /> <br /> 10digitphonenumber@txt.bellmobility.ca<br /> <br /> ==Bell Canada==<br /> <br /> 10digitphonenumber@bellmobility.ca<br /> <br /> ==Bell Mobility (Canada)==<br /> <br /> 10digitphonenumber@txt.bell.ca<br /> <br /> ==Bell Mobility==<br /> <br /> 10digitphonenumber@txt.bellmobility.ca<br /> <br /> ==Blue Sky Frog==<br /> <br /> 10digitphonenumber@blueskyfrog.com<br /> <br /> Bluegrass Cellular<br /> <br /> 10digitphonenumber@sms.bluecell.com<br /> <br /> Boost Mobile<br /> <br /> 10digitphonenumber@myboostmobile.com<br /> <br /> BPL Mobile<br /> <br /> 10digitphonenumber@bplmobile.com<br /> <br /> Carolina West Wireless<br /> <br /> 10digit10digitnumber@cwwsms.com<br /> <br /> Cellular One<br /> <br /> 10digitphonenumber@mobile.celloneusa.com<br /> <br /> Cellular South<br /> <br /> 10digitphonenumber@csouth1.com<br /> <br /> Centennial Wireless<br /> <br /> 10digitphonenumber@cwemail.com<br /> <br /> CenturyTel<br /> <br /> 10digitphonenumber@messaging.centurytel.net<br /> <br /> Cingular (Now AT&amp;T)<br /> <br /> 10digitphonenumber@txt.att.net<br /> <br /> Clearnet<br /> <br /> 10digitphonenumber@msg.clearnet.com<br /> <br /> ==Comcast==<br /> <br /> 10digitphonenumber@comcastpcs.textmsg.com<br /> <br /> Corr Wireless Communications<br /> <br /> 10digitphonenumber@corrwireless.net<br /> <br /> Dobson<br /> <br /> 10digitphonenumber@mobile.dobson.net<br /> <br /> Edge Wireless<br /> <br /> 10digitphonenumber@sms.edgewireless.com<br /> <br /> Fido<br /> <br /> 10digitphonenumber@fido.ca<br /> <br /> Golden Telecom<br /> <br /> 10digitphonenumber@sms.goldentele.com<br /> <br /> Helio<br /> <br /> 10digitphonenumber@messaging.sprintpcs.com<br /> <br /> Houston Cellular<br /> <br /> 10digitphonenumber@text.houstoncellular.net<br /> <br /> Idea Cellular<br /> <br /> 10digitphonenumber@ideacellular.net<br /> <br /> Illinois Valley Cellular<br /> <br /> 10digitphonenumber@ivctext.com<br /> <br /> Inland Cellular Telephone<br /> <br /> 10digitphonenumber@inlandlink.com<br /> <br /> MCI<br /> <br /> 10digitphonenumber@pagemci.com<br /> <br /> Metrocall<br /> <br /> 10digitpagernumber@page.metrocall.com<br /> <br /> Metrocall 2-way<br /> <br /> 10digitpagernumber@my2way.com<br /> <br /> Metro PCS<br /> <br /> 10digitphonenumber@mymetropcs.com<br /> <br /> Microcell<br /> <br /> 10digitphonenumber@fido.ca<br /> <br /> Midwest Wireless<br /> <br /> 10digitphonenumber@clearlydigital.com<br /> <br /> Mobilcomm<br /> <br /> 10digitphonenumber@mobilecomm.net<br /> <br /> MTS<br /> <br /> 10digitphonenumber@text.mtsmobility.com<br /> <br /> Nextel<br /> <br /> 10digitphonenumber@messaging.nextel.com<br /> <br /> OnlineBeep<br /> <br /> 10digitphonenumber@onlinebeep.net<br /> <br /> PCS One<br /> <br /> 10digitphonenumber@pcsone.net<br /> <br /> President's Choice<br /> <br /> 10digitphonenumber@txt.bell.ca<br /> <br /> Public Service Cellular<br /> <br /> 10digitphonenumber@sms.pscel.com<br /> <br /> ==Qwest==<br /> <br /> 10digitphonenumber@qwestmp.com<br /> <br /> Rogers AT&amp;T Wireless<br /> <br /> 10digitphonenumber@pcs.rogers.com<br /> <br /> Rogers Canada<br /> <br /> 10digitphonenumber@pcs.rogers.com<br /> <br /> Satellink<br /> <br /> 10digitpagernumber.pageme@satellink.net<br /> <br /> ==Southwestern Bell==<br /> <br /> 10digitphonenumber@email.swbw.com<br /> <br /> ==Sprint==<br /> <br /> 10digitphonenumber@messaging.sprintpcs.com<br /> <br /> Sumcom<br /> <br /> 10digitphonenumber@tms.suncom.com<br /> <br /> Surewest Communicaitons<br /> <br /> 10digitphonenumber@mobile.surewest.com<br /> <br /> ==T-Mobile==<br /> <br /> 10digitphonenumber@tmomail.net<br /> <br /> Telus<br /> <br /> 10digitphonenumber@msg.telus.com<br /> <br /> Tracfone<br /> <br /> 10digitphonenumber@txt.att.net<br /> <br /> Triton<br /> <br /> 10digitphonenumber@tms.suncom.com<br /> <br /> Unicel<br /> <br /> 10digitphonenumber@utext.com<br /> <br /> US Cellular<br /> <br /> 10digitphonenumber@email.uscc.net<br /> <br /> Solo Mobile<br /> <br /> 10digitphonenumber@txt.bell.ca<br /> <br /> ==Sprint==<br /> <br /> 10digitphonenumber@messaging.sprintpcs.com<br /> <br /> Sumcom<br /> <br /> 10digitphonenumber@tms.suncom.com<br /> <br /> Surewest Communicaitons<br /> <br /> 10digitphonenumber@mobile.surewest.com<br /> <br /> ==T-Mobile==<br /> <br /> 10digitphonenumber@tmomail.net<br /> <br /> Telus<br /> <br /> 10digitphonenumber@msg.telus.com<br /> <br /> Triton<br /> <br /> 10digitphonenumber@tms.suncom.com<br /> <br /> Unicel<br /> <br /> 10digitphonenumber@utext.com<br /> <br /> US Cellular<br /> <br /> 10digitphonenumber@email.uscc.net<br /> <br /> US West<br /> <br /> 10digitphonenumber@uswestdatamail.com<br /> <br /> ==Verizon==<br /> <br /> 10digitphonenumber@vtext.com<br /> <br /> Virgin Mobile<br /> <br /> 10digitphonenumber@vmobl.com<br /> <br /> Virgin Mobile Canada<br /> <br /> 10digitphonenumber@vmobile.ca<br /> <br /> West Central Wireless<br /> <br /> 10digitphonenumber@sms.wcc.net<br /> <br /> Western Wireless<br /> <br /> 10digitphonenumber@cellularonewest.com<br /> <br /> <br /> =International Carriers=<br /> <br /> <br /> ==Chennai RPG Cellular==<br /> <br /> phonenumber@rpgmail.net<br /> <br /> Chennai Skycell / Airtel<br /> <br /> phonenumber@airtelchennai.com<br /> <br /> Comviq<br /> <br /> number@sms.comviq.se<br /> <br /> Delhi Aritel<br /> <br /> phonenumber@airtelmail.com<br /> <br /> Delhi Hutch<br /> <br /> phonenumber@delhi.hutch.co.in<br /> <br /> DT T-Mobile<br /> <br /> phonenumber@t-mobile-sms.de<br /> <br /> Dutchtone / Orange-NL<br /> <br /> phonenumber@sms.orange.nl<br /> <br /> EMT<br /> <br /> phonenumber@sms.emt.ee<br /> <br /> Escotel<br /> <br /> phonenumber@escotelmobile.com<br /> <br /> German T-Mobile<br /> <br /> number@t-mobile-sms.de<br /> <br /> Goa BPLMobil<br /> <br /> phonenumber@bplmobile.com<br /> <br /> Golden Telecom<br /> <br /> phonenumber@sms.goldentele.com<br /> <br /> Gujarat Celforce<br /> <br /> phonenumber@celforce.com<br /> <br /> JSM Tele-Page<br /> <br /> pinnumber@jsmtel.com<br /> <br /> Kerala Escotel<br /> <br /> phonenumber@escotelmobile.com<br /> <br /> Kolkata Airtel<br /> <br /> phonenumber@airtelkol.com<br /> <br /> Kyivstar<br /> <br /> number@smsmail.lmt.lv<br /> <br /> Lauttamus Communication<br /> <br /> pagernumber@e-page.net<br /> <br /> LMT<br /> <br /> phonenumber@smsmail.lmt.lv<br /> <br /> Maharashtra BPL Mobile<br /> <br /> phonenumber@bplmobile.com<br /> <br /> Maharashtra Idea Cellular<br /> <br /> phonenumber@ideacellular.net<br /> <br /> Manitoba Telecom Systems<br /> <br /> phonenumber@text.mtsmobility.com<br /> <br /> Meteor<br /> <br /> phonenumber@mymeteor.ie<br /> <br /> MiWorld<br /> <br /> phonenumber@m1.com.sg<br /> <br /> Mobileone<br /> <br /> phonenumber@m1.com.sg<br /> <br /> Mobilfone<br /> <br /> phonenumber@page.mobilfone.com<br /> <br /> Mobility Bermuda<br /> <br /> phonenumber@ml.bm<br /> <br /> Mobistar Belgium<br /> <br /> phonenumber@mobistar.be<br /> <br /> Mobitel Tanzania<br /> <br /> phonenumber@sms.co.tz<br /> <br /> Mobtel Srbija<br /> <br /> phonenumber@mobtel.co.yu<br /> <br /> Movistar<br /> <br /> number@correo.movistar.net<br /> <br /> Mumbai BPL Mobile<br /> <br /> phonenumber@bplmobile.com<br /> <br /> Netcom<br /> <br /> phonenumber@sms.netcom.no<br /> <br /> Ntelos<br /> <br /> number@pcs.ntelos.com<br /> <br /> O2<br /> <br /> name@o2.co.uk<br /> <br /> O2<br /> <br /> number@o2imail.co.uk<br /> <br /> O2 (M-mail)<br /> <br /> number@mmail.co.uk<br /> <br /> One Connect Austria<br /> <br /> phonenumber@onemail.at<br /> <br /> OnlineBeep<br /> <br /> 10digitphonenumber@onlinebeep.net<br /> <br /> Optus Mobile<br /> <br /> phonenumber@optusmobile.com.au<br /> <br /> Orange<br /> <br /> phonenumber@orange.net<br /> <br /> Orange Mumbai<br /> <br /> phonenumber@orangemail.co.in<br /> <br /> Orange NL / Dutchtone<br /> <br /> phonenumber@sms.orange.nl<br /> <br /> Oskar<br /> <br /> phonenumber@mujoskar.cz<br /> <br /> P&amp;T Luxembourg<br /> <br /> phonenumber@sms.luxgsm.lu<br /> <br /> Personal Communication<br /> <br /> sms@pcom.ru (put the number in the subject line)<br /> <br /> Pondicherry BPL Mobile<br /> <br /> phonenumber@bplmobile.com<br /> <br /> Primtel<br /> <br /> phonenumber@sms.primtel.ru<br /> <br /> Safaricom<br /> <br /> phonenumber@safaricomsms.com<br /> <br /> Satelindo GSM<br /> <br /> phonenumber@satelindogsm.com<br /> <br /> SCS-900<br /> <br /> phonenumber@scs-900.ru<br /> <br /> SFR France<br /> <br /> phonenumber@sfr.fr<br /> <br /> Simple Freedom<br /> <br /> phonenumber@text.simplefreedom.net<br /> <br /> Smart Telecom<br /> <br /> phonenumber@mysmart.mymobile.ph<br /> <br /> Southern LINC<br /> <br /> 10digitphonenumber@page.southernlinc.com<br /> <br /> Sunrise Mobile<br /> <br /> phonenumber@mysunrise.ch<br /> <br /> Sunrise Mobile<br /> <br /> 10digitphonenumber@swmsg.com<br /> <br /> Surewest Communications<br /> <br /> phonenumber@freesurf.ch<br /> <br /> Swisscom<br /> <br /> phonenumber@bluewin.ch<br /> <br /> T-Mobile Austria<br /> <br /> phonenumber@sms.t-mobile.at<br /> <br /> T-Mobile Germany<br /> <br /> phonenumber@t-d1-sms.de<br /> <br /> T-Mobile UK<br /> <br /> phonenumber@t-mobile.uk.net<br /> <br /> Tamil Nadu BPL Mobile<br /> <br /> phonenumber@bplmobile.com<br /> <br /> Tele2 Latvia<br /> <br /> phonenumber@sms.tele2.lv<br /> <br /> Telefonica Movistar<br /> <br /> phonenumber@movistar.net<br /> <br /> Telenor<br /> <br /> phonenumber@mobilpost.no<br /> <br /> Teletouch<br /> <br /> 10digitpagernumber@pageme.teletouch.com<br /> <br /> Telia Denmark<br /> <br /> phonenumber@gsm1800.telia.dk<br /> <br /> TIM<br /> <br /> 10digitphonenumber@timnet.com<br /> <br /> TSR Wireless<br /> <br /> pagernumber@alphame.com<br /> <br /> UMC<br /> <br /> phonenumber@sms.umc.com.ua<br /> <br /> Uraltel<br /> <br /> phonenumber@sms.uraltel.ru<br /> <br /> Uttar Pradesh Escotel<br /> <br /> phonenumber@escotelmobile.com<br /> <br /> Vessotel<br /> <br /> phonenumber@pager.irkutsk.ru<br /> <br /> Vodafone Italy<br /> <br /> number@sms.vodafone.it<br /> <br /> Vodafone Japan<br /> <br /> phonenumber@c.vodafone.ne.jp<br /> <br /> Vodafone Japan<br /> <br /> phonenumber@h.vodafone.ne.jp<br /> <br /> Vodafone Japan<br /> <br /> phonenumber@t.vodafone.ne.jp<br /> <br /> Vodafone UK<br /> <br /> phonenumber@vodafone.net<br /> <br /> Wyndtell<br /> <br /> number@wyndtell.com<br /> <br /> <br /> =Old US &amp; Canadian Carriers (Most Not In Use)=<br /> <br /> <br /> Advantage Communications<br /> <br /> 10digitpagernumber@advantagepaging.com<br /> <br /> Airtouch Pagers<br /> <br /> 10digitpagernumber@myairmail.com<br /> <br /> AlphaNow<br /> <br /> pin@alphanow.net<br /> <br /> Ameritech Paging<br /> <br /> 10digitpagernumber@paging.acswireless.com<br /> <br /> American Messaging<br /> <br /> 10digitpagernumber@page.americanmessaging.net<br /> <br /> Ameritech Clearpath<br /> <br /> 10digitpagernumber@clearpath.acswireless.com<br /> <br /> Arch Pagers (PageNet)<br /> <br /> 10digitpagernumber@archwireless.net<br /> <br /> AT&amp;T<br /> <br /> 10digitphonenumber@mobile.att.net<br /> <br /> AT&amp;T Free2Go<br /> <br /> 10digitphonenumber@mmode.com<br /> <br /> AT&amp;T PCS<br /> <br /> 10digitphonenumber@mobile.att.net<br /> <br /> AT&amp;T Pocketnet PCS<br /> <br /> 10digitphonenumber@dpcs.mobile.att.net<br /> <br /> Beepwear<br /> <br /> 10digitphonenumber@beepwear.net<br /> <br /> Bell Atlantic<br /> <br /> 10digitphonenumber@message.bam.com<br /> <br /> Bell South<br /> <br /> 10digitphonenumber@wireless.bellsouth.com<br /> <br /> Bell South (Blackberry)<br /> <br /> 10digitphonenumber@bellsouthtips.com<br /> <br /> Bell South Mobility<br /> <br /> 10digitphonenumber@blsdcs.net<br /> <br /> Cellular One (East Coast)<br /> <br /> 10digitphonenumber@phone.cellone.net<br /> <br /> Cellular One (South West)<br /> <br /> 10digitphonenumber@swmsg.com<br /> <br /> Cellular One<br /> <br /> 10digitphonenumber@cellularone.txtmsg.com<br /> <br /> Cellular One<br /> <br /> 10digitphonenumber@cellularone.textmsg.com<br /> <br /> Cellular One<br /> <br /> 10digitphonenumber@cell1.textmsg.com<br /> <br /> Cellular One<br /> <br /> 10digitphonenumber@sbcemail.com<br /> <br /> Cellular One (West)<br /> <br /> 10digitphonenumber@mycellone.com<br /> <br /> Central Vermont Communications<br /> <br /> 10digitpagernumber@cvcpaging.com<br /> <br /> Cingular<br /> <br /> 10digitphonenumber@cingularme.com<br /> <br /> Communication Specialists<br /> <br /> 7digitpin@pageme.comspeco.net<br /> <br /> Cook Paging<br /> <br /> 10digitpagernumber@cookmail.com<br /> <br /> Corr Wireless Communications<br /> <br /> 10digitphonenumber@corrwireless.net<br /> <br /> Digi-Page / Page Kansas<br /> <br /> 10digitpagernumber@page.hit.net<br /> <br /> Galaxy Corporation<br /> <br /> 10digitpagernumber.epage@sendabeep.net<br /> <br /> GCS Paging<br /> <br /> 10digitpagernumber@webpager.us<br /> <br /> GrayLink / Porta-Phone<br /> <br /> 10digitpagernumber@epage.porta-phone.com<br /> <br /> GTE<br /> <br /> 10digitphonenumber@airmessage.net<br /> <br /> GTE<br /> <br /> 10digitphonenumber@gte.pagegate.net<br /> <br /> GTE<br /> <br /> 10digitphonenumber@messagealert.com<br /> <br /> Infopage Systems<br /> <br /> pinnumber@page.infopagesystems.com<br /> <br /> Indiana Paging Co<br /> <br /> 10digitphonenumber@inlandlink.com<br /> <br /> MCI<br /> <br /> 10digitphonenumber@pagemci.com<br /> <br /> Metrocall<br /> <br /> 10digitphonenumber@page.metrocall.com<br /> <br /> Mobilecom PA<br /> <br /> 10digitphonenumber@page.mobilcom.net<br /> <br /> Morris Wireless<br /> <br /> 10digitpagernumber@beepone.net<br /> <br /> Motient<br /> <br /> 10digitphonenumber@isp.com<br /> <br /> Nextel<br /> <br /> 10digitphonenumber@page.nextel.com<br /> <br /> Omnipoint<br /> <br /> 10digitphonenumber@omnipointpcs.com<br /> <br /> Pacific Bell<br /> <br /> 10digitphonenumber@pacbellpcs.net<br /> <br /> PageMart<br /> <br /> 7digitpinnumber@pagemart.net<br /> <br /> PageMart Canada<br /> <br /> 10digitpagernumber@pmcl.net<br /> <br /> PageNet Canada<br /> <br /> 10digitphonenumber@pagegate.pagenet.ca<br /> <br /> PageOne Northwest<br /> <br /> 10digitphonenumber@page1nw.com<br /> <br /> PCS One<br /> <br /> 10digitphonenumber@pcsone.net<br /> <br /> Powertel<br /> <br /> 10digitphonenumber@voicestream.net<br /> <br /> Price Communications<br /> <br /> 10digitphonenumber@mobilecell1se.com<br /> <br /> Primeco<br /> <br /> 10digitphonenumber@email.uscc.net<br /> <br /> ProPage<br /> <br /> 7digitpagernumber@page.propage.net<br /> <br /> Qualcomm<br /> <br /> name@pager.qualcomm.com<br /> <br /> RAM Page<br /> <br /> number@ram-page.com<br /> <br /> SBC Ameritech Paging<br /> <br /> 10digitpagernumber@paging.acswireless.com<br /> <br /> Skytel Pagers<br /> <br /> 10digitphonenumber@email.skytel.com<br /> <br /> ST Paging<br /> <br /> pin@page.stpaging.com<br /> <br /> Verizon Pagers<br /> <br /> 10digitpagernumber@myairmail.com<br /> <br /> Verizon PCS<br /> <br /> 10digitphonenumber@myvzw.com<br /> <br /> VoiceStream<br /> <br /> 10digitphonenumber@voicestream.net<br /> <br /> WebLink Wireless<br /> <br /> 10digitphonenumber@@airmessage.net<br /> <br /> WebLink Wireless<br /> <br /> 10digitphonenumber@pagemart.net<br /> <br /> West Central Wireless<br /> <br /> 10digitphonenumber@sms.wcc.net<br /> <br /> [[Category:Mail]]</div>

Qais http://www.initq.com/index.php/AMD-V_not_working_in_VirtualBox 2012-05-13T23:50:35Z

<p>Qais: </p> <hr /> <div>If you get a message when trying to run a 64bit OS in virtualbox to enable AMD-V the follow the below steps.<br /> <br /> First of all check your bios and make sure that SVM is enabled. This setting is under CPU settings.<br /> <br /> Boot up your machine and do '''grep --color svm /proc/cpuinfo'''. You should get some flags. If you do then you have svm support enabled. SVM will show up for AMD and for Intel you will get VMX.<br /> <br /> The only other reason VirtualBox is not seeing AMD-V is because another virtuallization mod is loaded for example kvm.<br /> <br /> 3.1.4 will contain a workaround for people with a broken BIOS and no option to update it.<br /> Set the VBOX_HWVIRTEX_IGNORE_SVM_IN_USE environment variable to true:<br /> <br /> set VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on Windows<br /> export VBOX_HWVIRTEX_IGNORE_SVM_IN_USE=true on Linux <br /> <br /> This will tell VirtualBox to ignore VERR_SVM_IN_USE and continue to use AMD-V. Note that this is a hack and dangerous if you run more than one hypervisor at the same time.<br /> <br /> [[Category:VirtualBox]]</div>

Qais http://www.initq.com/index.php/Basic_zfs_info 2012-02-27T08:03:59Z

<p>Qais: Created page with &quot;=Cache files= * /var/lib/zfs/zpool.cache * /etc/zfs/zpool.cache Category:ZFS&quot;</p> <hr /> <div>=Cache files=<br /> * /var/lib/zfs/zpool.cache<br /> * /etc/zfs/zpool.cache<br /> <br /> [[Category:ZFS]]</div>

Qais http://www.initq.com/index.php/Users_can_list_pools_in_zfs 2012-02-27T07:46:44Z

<p>Qais: Created page with &quot;Add the following to '''/etc/udev/rules.d/91-zfs-permissions.rules''' &lt;source lang=bash&gt; #Use this to add a group and more permissive permissions for zfs #so that you don't alway...&quot;</p> <hr /> <div>Add the following to '''/etc/udev/rules.d/91-zfs-permissions.rules'''<br /> &lt;source lang=bash&gt;<br /> #Use this to add a group and more permissive permissions for zfs<br /> #so that you don't always need run it as root. beware, users not root<br /> #can do nearly EVERYTHING, including, but not limited to destroying<br /> #volumes and deleting datasets. they CANNOT mount datasets or create new<br /> #volumes, export datasets via NFS, or other things that require root<br /> #permissions outside of ZFS.<br /> ACTION==&quot;add&quot;, KERNEL==&quot;zfs&quot;, MODE=&quot;0660&quot;, GROUP=&quot;zfs&quot;<br /> &lt;/source&gt;<br /> <br /> Add the group.<br /> &lt;source lang=bash&gt;<br /> root@debian:~# groupadd zfs<br /> root@debian:~# gpasswd -a username zfs <br /> &lt;/source&gt;<br /> <br /> Reboot and try the '''zfs list -t all'''<br /> [[Category:ZFS]]</div>

Qais http://www.initq.com/index.php/Enable_htaccess_files 2012-02-19T18:06:13Z

<p>Qais: </p> <hr /> <div>Check your httpd.conf or apache2.conf file for the following:<br /> <br /> &lt;source lang=bash&gt;<br /> AccessFileName .htaccess<br /> <br /> #<br /> # The following lines prevent .htaccess and .htpasswd files from being<br /> # viewed by Web clients.<br /> #<br /> &lt;Files ~ &quot;^\.ht&quot;&gt;<br /> Order allow,deny<br /> Deny from all<br /> Satisfy all<br /> &lt;/Files&gt;<br /> &lt;/source&gt;<br /> <br /> You also need to make sure you have a Directory defined in /etc/apache2/sites-enabled/000-default or your main httpd.conf or apache2.conf file like this:<br /> &lt;source lang=bash&gt;<br /> &lt;Directory /var/www&gt;<br /> Options FollowSymLinks<br /> AllowOverride ALL<br /> &lt;/Directory&gt;<br /> &lt;/source&gt;<br /> <br /> Now you can go make your .htaccess file in /var/www<br /> [[Category:Apache]]</div>

Qais http://www.initq.com/index.php/Run_shell_scripts_from_web 2012-02-19T15:50:13Z

<p>Qais: /* Simple show date script */</p> <hr /> <div>CGI stands for common gateway protocol. We are going to use some simple scripts to show you how you can run shell commands via apache.<br /> <br /> This setup will be for debian system.<br /> <br /> =Enable CGI=<br /> CGI is enabled in the /etc/apache2/sites-enabled/000-default<br /> <br /> &lt;source lang=bash&gt;<br /> ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/<br /> &lt;Directory &quot;/usr/lib/cgi-bin&quot;&gt;<br /> AllowOverride None<br /> Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch<br /> Order allow,deny<br /> Allow from all<br /> &lt;/Directory&gt;<br /> &lt;/source&gt;<br /> <br /> Restart apache is you made any changes<br /> <br /> &lt;source lang=bash&gt;<br /> root@debian60:/etc/apache2/sites-enabled# apachectl configtest<br /> Syntax OK<br /> root@debian60:/etc/apache2/sites-enabled# apachectl restart<br /> &lt;/source&gt;<br /> <br /> =Simple show date script=<br /> Edit /usr/lib/cgi-bin/date.cgi and make it +x. Put the following in it<br /> &lt;source lang=bash&gt;<br /> #!/bin/bash<br /> # get today's date<br /> OUTPUT=&quot;$(date)&quot;<br /> # You must add following two lines before<br /> # outputting data to the web browser from shell<br /> # script<br /> echo &quot;Content-type: text/html&quot;<br /> echo &quot;&quot;<br /> echo &quot;&lt;html&gt;&lt;head&gt;&lt;title&gt;Demo&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&quot;<br /> echo &quot;Today is &lt;pre&gt; $OUTPUT &lt;/pre&gt; &lt;br&gt;&quot;<br /> echo &quot;Current directory is $(pwd) &lt;br&gt;&quot;<br /> echo &quot;Shell Script name is $0&quot;<br /> echo &quot;&lt;/body&gt;&lt;/html&gt;&quot;<br /> &lt;/source&gt;<br /> <br /> result will show<br /> &lt;source lang=bash&gt;<br /> Today is Sat Feb 18 12:06:15 CST 2012<br /> Current directory is /usr/lib/cgi-bin<br /> Shell Script name is /usr/lib/cgi-bin/date.cgi <br /> &lt;/source&gt;<br /> [[Category:CGI]]</div>

Qais http://www.initq.com/index.php/Nc 2012-02-16T03:44:09Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:nc}}<br /> =Listen on any port=<br /> * nc -l 3333<br /> Go to another machine and '''nc &lt;ip&gt; 3333'''. anything you type will be echoed. You can also use this for testing firewall rules by running nc on different ports and then trying to nmap or telnet to it.<br /> <br /> =Transfering Files=<br /> In the very same way it can be used to transfer files between two computers. You can create a server that serves the file with the following:<br /> &lt;source lang=bash&gt;<br /> $ cat backup.iso | nc -l 3333<br /> &lt;/source&gt;<br /> Receive backup.iso on the client machine with the following:<br /> &lt;source lang=bash&gt;<br /> $ nc 192.168.0.1 3333 &gt; backup.iso<br /> &lt;/source&gt;<br /> As you may have noticed, netcat does not show any info about the progress of the data transfer. This is inconvenient when dealing with large files. In such cases, a pipe-monitoring utility like pv can be used to show a progress indicator. For example, the following shows the total amount of data that has been transfered in real-time on the server side:<br /> &lt;source lang=bash&gt;<br /> $ cat backup.iso | pv -b | nc -l 3333<br /> &lt;/source&gt;<br /> Of course, the same can be implemented on the client side by piping netcat’s output through pv:<br /> &lt;source lang=bash&gt;<br /> $ nc 192.168.0.1 3333 | pv -b &gt; backup.iso<br /> &lt;/source&gt;<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Mysql_prompt_cheet_sheet 2012-02-14T16:11:55Z

<p>Qais: </p> <hr /> <div>=Run a script=<br /> * mysql&gt; SOURCE /home/bob/my_commands.sql;<br /> <br /> =List all users=<br /> * mysql&gt; select User from mysql.user;<br /> [[Category:Mysql]]</div>

Qais http://www.initq.com/index.php/Backup_and_Restore_mysql 2012-02-14T15:35:42Z

<p>Qais: Created page with &quot;How to backup and Restore mysql: * backup: # mysqldump -u root -p[root_password] [database_name] &gt; dumpfilename.sql * restore:# mysql -u root -p[root_password] [database_name] ...&quot;</p> <hr /> <div>How to backup and Restore mysql:<br /> <br /> * backup: # mysqldump -u root -p[root_password] [database_name] &gt; dumpfilename.sql<br /> <br /> * restore:# mysql -u root -p[root_password] [database_name] &lt; dumpfilename.sql<br /> <br /> [[Category:Mysql]]</div>

Qais http://www.initq.com/index.php/Installing_nagios 2012-02-12T15:59:04Z

<p>Qais: /* Password for nagios */</p> <hr /> <div>=Debian Install=<br /> At the writing of this article nagios-3 was the latest version.<br /> &lt;source lang=bash&gt;<br /> root@debian60:~# apt-get install nagios3-core<br /> Reading package lists... Done<br /> Building dependency tree <br /> Reading state information... Done<br /> The following extra packages will be installed:<br /> fping libmysqlclient16 libpq5 libradiusclient-ng2 mysql-common nagios-plugins nagios-plugins-basic nagios-plugins-standard nagios3-common qstat samba-common samba-common-bin<br /> smbclient<br /> Suggested packages:<br /> nagios3 nagios-nrpe-plugin cifs-utils<br /> The following NEW packages will be installed:<br /> fping libmysqlclient16 libpq5 libradiusclient-ng2 mysql-common nagios-plugins nagios-plugins-basic nagios-plugins-standard nagios3-common nagios3-core qstat samba-common<br /> samba-common-bin smbclient<br /> 0 upgraded, 14 newly installed, 0 to remove and 167 not upgraded.<br /> Need to get 26.2 MB of archives.<br /> After this operation, 76.7 MB of additional disk space will be used.<br /> Do you want to continue [Y/n]? Y<br /> Get:1 http://ftp.us.debian.org/debian/ squeeze/main fping amd64 2.4b2-to-ipv6-16.1 [33.9 kB]<br /> Get:2 http://ftp.us.debian.org/debian/ squeeze/main mysql-common all 5.1.49-3 [70.9 kB]<br /> Get:3 http://ftp.us.debian.org/debian/ squeeze/main libmysqlclient16 amd64 5.1.49-3 [1,985 kB]<br /> Get:4 http://ftp.us.debian.org/debian/ squeeze/main libpq5 amd64 8.4.10-0squeeze1 [165 kB]<br /> Get:5 http://ftp.us.debian.org/debian/ squeeze/main libradiusclient-ng2 amd64 0.5.6-1.1 [39.9 kB]<br /> Get:6 http://ftp.us.debian.org/debian/ squeeze/main nagios-plugins-basic amd64 1.4.15-3squeeze1 [1,010 kB]<br /> Get:7 http://ftp.us.debian.org/debian/ squeeze/main nagios3-common all 3.2.1-2 [78.7 kB] <br /> Get:8 http://ftp.us.debian.org/debian/ squeeze/main nagios3-core amd64 3.2.1-2 [271 kB] <br /> Get:9 http://ftp.us.debian.org/debian/ squeeze/main qstat amd64 2.11-3 [145 kB] <br /> Get:10 http://ftp.us.debian.org/debian/ squeeze/main samba-common all 2:3.5.6~dfsg-3squeeze6 [388 kB] <br /> Get:11 http://ftp.us.debian.org/debian/ squeeze/main samba-common-bin amd64 2:3.5.6~dfsg-3squeeze6 [6,378 kB] <br /> Get:12 http://ftp.us.debian.org/debian/ squeeze/main smbclient amd64 2:3.5.6~dfsg-3squeeze6 [15.2 MB] <br /> Get:13 http://ftp.us.debian.org/debian/ squeeze/main nagios-plugins-standard amd64 1.4.15-3squeeze1 [429 kB] <br /> Get:14 http://ftp.us.debian.org/debian/ squeeze/main nagios-plugins all 1.4.15-3squeeze1 [21.3 kB] <br /> Fetched 26.2 MB in 53s (487 kB/s) <br /> Preconfiguring packages ...<br /> Selecting previously deselected package fping.<br /> (Reading database ... 119368 files and directories currently installed.)<br /> Unpacking fping (from .../fping_2.4b2-to-ipv6-16.1_amd64.deb) ...<br /> Selecting previously deselected package mysql-common.<br /> Unpacking mysql-common (from .../mysql-common_5.1.49-3_all.deb) ...<br /> Selecting previously deselected package libmysqlclient16.<br /> Unpacking libmysqlclient16 (from .../libmysqlclient16_5.1.49-3_amd64.deb) ...<br /> Selecting previously deselected package libpq5.<br /> Unpacking libpq5 (from .../libpq5_8.4.10-0squeeze1_amd64.deb) ...<br /> Selecting previously deselected package libradiusclient-ng2.<br /> Unpacking libradiusclient-ng2 (from .../libradiusclient-ng2_0.5.6-1.1_amd64.deb) ...<br /> Selecting previously deselected package nagios-plugins-basic.<br /> Unpacking nagios-plugins-basic (from .../nagios-plugins-basic_1.4.15-3squeeze1_amd64.deb) ...<br /> Selecting previously deselected package nagios3-common.<br /> Unpacking nagios3-common (from .../nagios3-common_3.2.1-2_all.deb) ...<br /> Selecting previously deselected package nagios3-core.<br /> Unpacking nagios3-core (from .../nagios3-core_3.2.1-2_amd64.deb) ...<br /> Selecting previously deselected package qstat.<br /> Unpacking qstat (from .../qstat_2.11-3_amd64.deb) ...<br /> Selecting previously deselected package samba-common.<br /> Unpacking samba-common (from .../samba-common_2%3a3.5.6~dfsg-3squeeze6_all.deb) ...<br /> Selecting previously deselected package samba-common-bin.<br /> Unpacking samba-common-bin (from .../samba-common-bin_2%3a3.5.6~dfsg-3squeeze6_amd64.deb) ...<br /> Selecting previously deselected package smbclient.<br /> Unpacking smbclient (from .../smbclient_2%3a3.5.6~dfsg-3squeeze6_amd64.deb) ...<br /> Selecting previously deselected package nagios-plugins-standard.<br /> Unpacking nagios-plugins-standard (from .../nagios-plugins-standard_1.4.15-3squeeze1_amd64.deb) ...<br /> Selecting previously deselected package nagios-plugins.<br /> Unpacking nagios-plugins (from .../nagios-plugins_1.4.15-3squeeze1_all.deb) ...<br /> Processing triggers for man-db ...<br /> Setting up fping (2.4b2-to-ipv6-16.1) ...<br /> Setting up mysql-common (5.1.49-3) ...<br /> Setting up libmysqlclient16 (5.1.49-3) ...<br /> Setting up libpq5 (8.4.10-0squeeze1) ...<br /> Setting up libradiusclient-ng2 (0.5.6-1.1) ...<br /> Setting up nagios-plugins-basic (1.4.15-3squeeze1) ...<br /> <br /> Creating config file /etc/nagios-plugins/config/apt.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/dhcp.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/disk.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/dummy.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ftp.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/http.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/load.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/mail.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/news.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ntp.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ping.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/procs.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/real.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ssh.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/tcp_udp.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/telnet.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/users.cfg with new version<br /> Setting up nagios3-common (3.2.1-2) ...<br /> Adding system-user for nagios<br /> Starting nagios3 monitoring daemon: nagios3.<br /> Setting up nagios3-core (3.2.1-2) ...<br /> Setting up qstat (2.11-3) ...<br /> Setting up samba-common (2:3.5.6~dfsg-3squeeze6) ...<br /> <br /> Creating config file /etc/samba/smb.conf with new version<br /> Setting up samba-common-bin (2:3.5.6~dfsg-3squeeze6) ...<br /> update-alternatives: using /usr/bin/nmblookup.samba3 to provide /usr/bin/nmblookup (nmblookup) in auto mode.<br /> update-alternatives: using /usr/bin/net.samba3 to provide /usr/bin/net (net) in auto mode.<br /> update-alternatives: using /usr/bin/testparm.samba3 to provide /usr/bin/testparm (testparm) in auto mode.<br /> Setting up smbclient (2:3.5.6~dfsg-3squeeze6) ...<br /> Setting up nagios-plugins-standard (1.4.15-3squeeze1) ...<br /> <br /> Creating config file /etc/nagios-plugins/config/breeze.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/disk-smb.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/dns.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/flexlm.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/fping.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/games.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/hppjd.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ifstatus.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/ldap.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/mailq.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/mrtg.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/mysql.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/netware.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/nt.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/pgsql.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/radius.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/rpc-nfs.cfg with new version<br /> <br /> Creating config file /etc/nagios-plugins/config/snmp.cfg with new version<br /> Setting up nagios-plugins (1.4.15-3squeeze1) ...<br /> root@debian60:~#<br /> &lt;/source&gt;<br /> <br /> After this install apache and nagios-cgi.<br /> <br /> &lt;source lang=bash&gt;<br /> apt-get install apache2-mpm-worker<br /> apt-get install nagios3-cgi<br /> &lt;/source&gt;<br /> <br /> =Password for nagios=<br /> Passwords are kept in <br /> * /etc/nagios3/htpasswd.users<br /> <br /> During the install you will be asked to put in a default nagiosadmin password. if you forget then:<br /> * htpasswd /etc/nagios3/htpasswd.users nagiosadmin<br /> to make a new password.<br /> [[Category:Nagios]]</div>

Qais http://www.initq.com/index.php/ACL_utilities 2012-02-10T03:53:59Z

<p>Qais: /* Remove all acl */</p> <hr /> <div>The Access Control List (ACL) feature extends the model to allow much finer control: you can specify permissions for each individual user and group defined in your system.<br /> <br /> =Turn ACL on the partition=<br /> As root, edit /etc/fstab. Find the partition that you want ACL enabled, and add the mount option acl.<br /> &lt;source lang=bash&gt;<br /> /dev/mapper/star-home /home ext3 defaults,acl 0 2<br /> &lt;/source&gt;<br /> =Remount your partition=<br /> &lt;source lang=bash&gt;<br /> mount -o remount /<br /> &lt;/source&gt;<br /> <br /> You can also do:<br /> * mount -o remount,acl /<br /> <br /> =Get ACL package=<br /> &lt;source lang=bash&gt;<br /> $ apt-get install acl<br /> &lt;/source&gt;<br /> =Our test users and groups=<br /> Do all this as root<br /> * mkdir /opt/projections<br /> * groupadd sales<br /> * groupadd marketing<br /> * useradd -m tester<br /> * useradd -m sales1<br /> * useradd -m marketing1<br /> * usermod -G sales sales1<br /> * usermod -G marketing marketing1<br /> * id sales1<br /> * id marketing1<br /> <br /> You should see that users sales1 and marketing1 belong to two groups.<br /> <br /> =Set permissions for a file=<br /> Create a file in /home/lexiana called targets.txt.<br /> * touch /home/lexiana/targets.txt<br /> <br /> Let's set permissions.<br /> * setfacl -m group:sales:rw-,group:marketing:rw- targets.txt<br /> &lt;source lang=bash&gt;<br /> # getfacl targets.txt <br /> # file: targets.txt<br /> # owner: root<br /> # group: root<br /> user::rw-<br /> group::r--<br /> group:sales:rw-<br /> group:marketing:rw-<br /> mask::rw-<br /> other::r--<br /> &lt;/source&gt;<br /> <br /> To test:<br /> * su - sales1<br /> * vi /home/lexiana/targets.txt<br /> <br /> You should be able to edit this file but should not be able to add anything else in /home/lexiana<br /> <br /> =Set permissions on a directory=<br /> * setfacl -m user:tester:rwx,group:sales:rwx,group:marketing:rwx /opt/projections/<br /> &lt;source lang=bash&gt;<br /> root@debian60:/opt# getfacl projections/<br /> # file: projections/<br /> # owner: root<br /> # group: root<br /> user::rwx<br /> user:lexiana:rwx<br /> user:tester:rwx<br /> group::r-x<br /> group:sales:rwx<br /> group:marketing:rwx<br /> mask::rwx<br /> other::r-x<br /> &lt;/source&gt;<br /> <br /> Test by swicthing to user tester and writing and deleting files in /opt/projections<br /> =Grant user rwx=<br /> &lt;source lang=bash&gt;<br /> setfacl -m u:bob:rwx /data1/foo.txt<br /> &lt;/source&gt;<br /> <br /> =Grant group read write=<br /> &lt;source lang=bash&gt;<br /> setfacl -m g:peeps:rw /data1/foo.txt<br /> &lt;/source&gt;<br /> =Remove ACL permissions=<br /> &lt;source lang=bash&gt;<br /> setfacl -x u:bob /data1/foo.txt<br /> &lt;/source&gt;<br /> <br /> =Default ACL permissions on a directory=<br /> &lt;source lang=bash&gt;<br /> setfacl -m d:g:peeps:rw /data1/stuff/<br /> &lt;/source&gt;<br /> <br /> =Revoke write permission for everyone=<br /> &lt;source lang=bash&gt;<br /> setfacl -m m::rx /data1/foo.txt<br /> &lt;/source&gt;<br /> <br /> =Remove all acl=<br /> &lt;source lang=bash&gt;<br /> setfacl --remove-all -R apache2/<br /> &lt;/source&gt;<br /> [[Category:Linux_Articles]]</div>

Qais http://www.initq.com/index.php/Reset_the_Root_Password_for_mysql 2012-02-08T16:42:47Z

<p>Qais: Created page with &quot;1. Log on to your system as Administrator. 2. mysqld_safe --skip-grant-tables 3. mysql --user=root mysql 4. update user set Password=PASSWORD('new-password') where user='root...&quot;</p> <hr /> <div>1. Log on to your system as Administrator.<br /> <br /> 2. mysqld_safe --skip-grant-tables <br /> <br /> 3. mysql --user=root mysql<br /> <br /> 4. update user set Password=PASSWORD('new-password') where user='root';<br /> flush privileges;<br /> exit;<br /> <br /> [[Category:Mysql]]</div>

Qais http://www.initq.com/index.php/Ldconfig 2012-02-08T15:03:17Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:ldconfig}}<br /> <br /> Ldconfig is a basic system program which determines run-time linkbindings between ld.so and shared libraries. Ldconfig scans a running system and sets up the symbolic links that are used to load shared libraries properly. It also creates a cache (/etc/ld.so.cache) which speeds the loading of programs which use shared libraries. <br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> [root@linapp20 ~]# ldconfig -p | grep libgd<br /> libgdk_pixbuf_xlib-2.0.so.0 (libc6,x86-64) =&gt; /usr/lib64/libgdk_pixbuf_xlib-2.0.so.0<br /> libgdk_pixbuf-2.0.so.0 (libc6,x86-64) =&gt; /usr/lib64/libgdk_pixbuf-2.0.so.0<br /> libgdk-x11-2.0.so.0 (libc6,x86-64) =&gt; /usr/lib64/libgdk-x11-2.0.so.0<br /> libgdbm.so.2 (libc6,x86-64) =&gt; /usr/lib64/libgdbm.so.2<br /> libgd.so.2 (libc6,x86-64) =&gt; /usr/lib64/libgd.so.2<br /> libgd.so (libc6,x86-64) =&gt; /usr/lib64/libgd.so<br /> &lt;/source&gt;<br /> <br /> To check your glibc version do<br /> * ldd --version<br /> <br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Nagios.cfg 2012-01-30T04:08:52Z

<p>Qais: Created page with &quot;Main Config File for Nagios Category:Nagios&quot;</p> <hr /> <div>Main Config File for Nagios<br /> <br /> <br /> <br /> [[Category:Nagios]]</div>

Qais http://www.initq.com/index.php/Basic_Info 2012-01-30T01:17:12Z

<p>Qais: /* Nagios Files */</p> <hr /> <div>=Monitoring tools=<br /> There are many like Big Brother, OpenNMS, OpenView and SysMon.<br /> <br /> =Nagios can monotor=<br /> * Ping to see if host is reachable<br /> <br /> * Services such as DHCP, DNS, FTP, SSH, Telnet, HTTP, NTP, POP3, IMAP, SMTP etc.<br /> <br /> * Database servers such as MySQL, Postgres, Oracle, SQL Server etc.<br /> <br /> * Application level information (Apache, Postfix, LDAP, Citrix etc.)<br /> <br /> =Installing Nagios=<br /> * apt-get install nagios3<br /> <br /> =Default password=<br /> The default opassword goes in /etc/nagios3/htpasswd.users. <br /> <br /> =Nagios Files=<br /> * nagios.cfg<br /> The main configuration file (usually /usr/local/nagios/etc/nagios.cfg) contains a number of directives that affect how Nagios operates. This config file is read by both the Nagios process and the CGIs. This is the first configuration file you're going to want to create or edit. <br /> <br /> * resource.cfg<br /> Resource files can be used to store user-defined macros. Resource files can also contain other information (like database connection settings), although this will depend on how you've compiled Nagios. The main point of having resource files is to use them to store sensitive configuration information and not make them available to the CGIs.<br /> <br /> * cgi.cfg<br /> The CGI configuration file (usually /usr/local/nagios/etc/cgi.cfg) contains a number of directives that affect the operation of the CGIs. <br /> <br /> * object files<br /> These are the object configuration files in which you define hosts, host groups, contacts, contact groups, services, etc. You can split your object definitions across several config files if you wish (as shown below), or keep them all in a single config file.<br /> <br /> You can specify individual object config files as shown below:<br /> <br /> cfg_file=/etc/nagios3/objects/commands.cfg<br /> <br /> cfg_file=/etc/nagios3/objects/contacts.cfg<br /> <br /> cfg_file=/etc/nagios3/objects/timeperiods.cfg<br /> <br /> cfg_file=/etc/nagios3/objects/templates.cfg<br /> <br /> Definitions for monitoring a Windows machine<br /> <br /> cfg_file=/etc/nagios3/objects/windows.cfg<br /> <br /> Definitions for monitoring a router/switch<br /> <br /> cfg_file=/etc/nagios3/objects/switch.cfg<br /> <br /> Definitions for monitoring a network printer<br /> <br /> You can also tell Nagios to process all config files (with a .cfg extension) in a particular directory by using the cfg_dir<br /> <br /> directive as shown below:<br /> <br /> cfg_dir=/etc/nagios3/servers<br /> <br /> cfg_dir=/etc/nagios3/printers<br /> <br /> cfg_dir=/etc/nagios3/switches<br /> <br /> cfg_dir=/etc/nagios3/routers<br /> <br /> =Enable Nagios=<br /> * deb = /etc/default/nagios3<br /> * rpm = /etc/rc.conf<br /> =Verify config=<br /> * /usr/sbin/nagios3 -v nagios.cfg<br /> =Check config=<br /> * /usr/sbin/nagios3 -s nagios.cfg<br /> [[Category:Nagios]]</div>

Qais http://www.initq.com/index.php/RCS_MINI-HOWTO 2012-01-25T03:35:04Z

<p>Qais: /* Cheat sheet */</p> <hr /> <div>GNU Revision Control System, under Linux.<br /> <br /> =Creating an archive=<br /> &lt;source lang=bash&gt;<br /> lexiana@initq:~/junk$ rcs -i file.c<br /> RCS file: file.c,v<br /> enter description, terminated with single '.' or end of file:<br /> NOTE: This is NOT the log message!<br /> &gt;&gt; this is my first file.<br /> &gt;&gt; .<br /> done<br /> lexiana@initq:~/junk$ ls -la<br /> total 12<br /> drwxrwxr-x 2 lexiana lexiana 4096 2012-01-24 21:34 .<br /> drwxr-xr-x 62 lexiana lexiana 4096 2012-01-24 21:23 ..<br /> -r--r--r-- 1 lexiana lexiana 88 2012-01-24 21:34 file.c,v<br /> &lt;/source&gt;<br /> =Check out files=<br /> &lt;source lang=bash&gt;<br /> lexiana@initq:~/junk$ co -l file.c<br /> file.c,v --&gt; file.c<br /> no revisions present; generating empty revision 0.0<br /> co: warning: no revisions, so nothing can be locked<br /> done<br /> lexiana@initq:~/junk$ ls -la<br /> total 12<br /> drwxrwxr-x 2 lexiana lexiana 4096 2012-01-24 21:45 .<br /> drwxr-xr-x 62 lexiana lexiana 4096 2012-01-24 21:40 ..<br /> -rw-r--r-- 1 lexiana lexiana 0 2012-01-24 21:45 file.c<br /> -r--r--r-- 1 lexiana lexiana 89 2012-01-24 21:45 file.c,v<br /> &lt;/source&gt;<br /> <br /> Now you can edit file.c<br /> <br /> =Check in=<br /> &lt;source lang=bash&gt;<br /> lexiana@initq:~/junk$ ci -l file.c<br /> file.c,v &lt;-- file.c<br /> new revision: 1.3; previous revision: 1.2<br /> enter log message, terminated with single '.' or end of file:<br /> &gt;&gt; made 3rd change.<br /> &gt;&gt; .<br /> done<br /> lexiana@initq:~/junk$ ls -la<br /> total 16<br /> drwxrwxr-x 2 lexiana lexiana 4096 2012-01-24 21:49 .<br /> drwxr-xr-x 62 lexiana lexiana 4096 2012-01-24 21:49 ..<br /> -rw-r--r-- 1 lexiana lexiana 50 2012-01-24 21:49 file.c<br /> -r--r--r-- 1 lexiana lexiana 510 2012-01-24 21:49 file.c,v<br /> &lt;/source&gt;<br /> =History Status=<br /> &lt;source lang=bash&gt;<br /> rlog -b file.c<br /> &lt;/source&gt;<br /> <br /> =Cheat sheet=<br /> &lt;source lang=bash&gt;<br /> mkdir RCS<br /> rcs -i prod-processor.ksh<br /> co -l prod-processor.ksh<br /> vi prod-processor.ksh<br /> ci prod-processor.ksh<br /> co -r prod-processor.ksh<br /> &lt;/source&gt;<br /> [[Category:RCS]]</div>

Qais http://www.initq.com/index.php/Vpnc_error 2011-12-29T15:57:05Z

<p>Qais: Created page with &quot;=Error: either &quot;to&quot; is duplicate, or &quot;ipid&quot; is a garbage.= To fixthi edit * /etc/vpnc/vpnc-script line 119 replace line with &lt;source lang=bash&gt; sed 's/cache//;s/metric \?[0-9]\+...&quot;</p> <hr /> <div>=Error: either &quot;to&quot; is duplicate, or &quot;ipid&quot; is a garbage.=<br /> To fixthi edit<br /> * /etc/vpnc/vpnc-script line 119<br /> replace line with<br /> <br /> &lt;source lang=bash&gt;<br /> sed 's/cache//;s/metric \?[0-9]\+ [0-9]\+//g;s/hoplimit[0-9]\+//g;s/ipid 0x....//g'<br /> &lt;/source&gt;<br /> [[Caegory:vpnc]]</div>

Qais http://www.initq.com/index.php/Telnet 2011-12-29T15:19:05Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:telnet}} Category:Linux_Commands&quot;</p> <hr /> <div>{{DISPLAYTITLE:telnet}}<br /> <br /> [[Category:Linux_Commands]]</div>

Qais http://www.initq.com/index.php/Ping 2011-12-27T14:40:56Z

<p>Qais: /* --c flag count */</p> <hr /> <div>{{DISPLAYTITLE:ping}}<br /> <br /> =ping flood=<br /> Only root can use the -f flag.<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> # ping -f jump221<br /> PING jump221 (161.89.145.221) 56(84) bytes of data.<br /> .^C <br /> --- jump221 ping statistics ---<br /> 1507 packets transmitted, 1506 received, 0% packet loss, time 23438ms<br /> rtt min/avg/max/mdev = 17.587/21.271/46.510/2.949 ms, pipe 4, ipg/ewma 15.563/20.038 ms<br /> &lt;/source&gt;<br /> <br /> 1% or 2% packet loss is tolerable but not anymore. If you have more then you have network issues.<br /> <br /> =-I switch=<br /> Use the -I flag to use a specific interface.<br /> <br /> =-n flag=<br /> Numeric output only. No attempt will be made to lookup symbolic names for host addresses.<br /> =--c flag count=<br /> &lt;source lang=bash&gt;<br /> a507394@aowarll271:~$ ping -c 3 jump221<br /> PING jump221 (161.89.145.221) 56(84) bytes of data.<br /> 64 bytes from jump221 (161.89.145.221): icmp_req=1 ttl=58 time=25.1 ms<br /> 64 bytes from jump221 (161.89.145.221): icmp_req=2 ttl=58 time=19.1 ms<br /> 64 bytes from jump221 (161.89.145.221): icmp_req=3 ttl=58 time=22.0 ms<br /> <br /> --- jump221 ping statistics ---<br /> 3 packets transmitted, 3 received, 0% packet loss, time 2002ms<br /> rtt min/avg/max/mdev = 19.138/22.110/25.135/2.451 ms<br /> <br /> &lt;/source&gt;<br /> =-D date=<br /> Unix date the ping results.<br /> =-t ttl= <br /> Set the IP Time to Live.<br /> =-s packetsize=<br /> Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data.<br /> [[Category:Linux_Commands]]</div>

Qais http://www.initq.com/index.php/Nmap 2011-10-23T16:43:36Z

<p>Qais: /* OS DETECTION */</p> <hr /> <div>{{DISPLAYTITLE:nmap}}<br /> <br /> =OS DETECTION=<br /> -O: Enable OS detection<br /> --osscan-limit: Limit OS detection to promising targets<br /> --osscan-guess: Guess OS more aggressively<br /> &lt;source lang=bash&gt;<br /> nmap -O jump221<br /> <br /> Starting Nmap 5.21 ( http://nmap.org ) at 2011-12-27 12:34 CST<br /> Nmap scan report for jump221 (161.89.145.221)<br /> Host is up (0.023s latency).<br /> Not shown: 995 closed ports<br /> PORT STATE SERVICE<br /> 21/tcp open ftp<br /> 22/tcp open ssh<br /> 80/tcp open http<br /> 111/tcp open rpcbind<br /> 3306/tcp open mysql<br /> Device type: general purpose<br /> Running: Linux 2.6.X<br /> OS details: Linux 2.6.18 (CentOS 5.1, x86)<br /> Network Distance: 6 hops<br /> <br /> OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 8.44 seconds<br /> <br /> &lt;/source&gt;<br /> <br /> * nmap -A -T4 scanme.nmap.org<br /> <br /> The only Nmap arguments used in this example are -A, to enable OS and version detection, script scanning, and traceroute; -T4 for faster execution; and then the two target hostnames.<br /> <br /> =Multiple address=<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> $ nmap 161.89.145.220-221<br /> <br /> Starting Nmap 5.21 ( http://nmap.org ) at 2011-12-27 12:29 CST<br /> Nmap scan report for jump220 (161.89.145.220)<br /> Host is up (0.024s latency).<br /> Not shown: 985 closed ports<br /> PORT STATE SERVICE<br /> 22/tcp open ssh<br /> 23/tcp open telnet<br /> 135/tcp open msrpc<br /> 139/tcp open netbios-ssn<br /> 445/tcp open microsoft-ds<br /> 1025/tcp open NFS-or-IIS<br /> 1033/tcp open netinfo<br /> 1039/tcp open unknown<br /> 2301/tcp open compaqdiag<br /> 2381/tcp open unknown<br /> 3389/tcp open ms-term-serv<br /> 5555/tcp open freeciv<br /> 5800/tcp open vnc-http<br /> 5900/tcp open vnc<br /> 8081/tcp open blackice-icecap<br /> <br /> Nmap scan report for jump221 (161.89.145.221)<br /> Host is up (0.025s latency).<br /> Not shown: 995 closed ports<br /> PORT STATE SERVICE<br /> 21/tcp open ftp<br /> 22/tcp open ssh<br /> 80/tcp open http<br /> 111/tcp open rpcbind<br /> 3306/tcp open mysql<br /> <br /> Nmap done: 2 IP addresses (2 hosts up) scanned in 7.87 seconds<br /> <br /> &lt;/source&gt;<br /> <br /> <br /> <br /> &lt;source lang=&quot;bash&quot;&gt;<br /> <br /> &lt;/source&gt;<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/NTP_Server 2011-10-20T14:29:47Z

<p>Qais: /* Kernel Time */</p> <hr /> <div>The Network Time Protocol (NTP) is a protocol used to help synchronize your Linux system's clock with an accurate time source. There are that allow the general public to synchronize with them. They are divided into two types: <br /> <br /> * Stratum 1: NTP sites using an atomic clock for timing.<br /> * Stratum 2: NTP sites with slightly less accurate time sources. <br /> <br /> It is good practice to have at least one server on your network be the local time server for all your other devices. This makes the correlation of system events on different systems much easier. It also reduces Internet bandwidth usage due to NTP traffic and reduces the need to manage firewall rules for each NTP client on your network. Sometimes, not all your servers will have Internet access; in such cases you'll need a central server that all can access. <br /> <br /> =Download and install=<br /> ==Debian==<br /> * apt-get install ntp<br /> <br /> ==RedHat==<br /> * yum install ntp<br /> * chkconfig ntpd on<br /> <br /> =/etc/ntp.conf File=<br /> The /etc/ntp.conf file is the main configuration file for Linux NTP in which you place the IP addresses of the stratum 1 and stratum 2 servers you want to use. Here are the steps to create a configuration file using a pair of sample Internet-based NTP servers: <br /> <br /> ==Different ntp servers==<br /> 1) First we specify the servers you're interested in: <br /> &lt;source lang=bash&gt;<br /> server 0.rhel.pool.ntp.org<br /> server 1.rhel.pool.ntp.org<br /> server 2.rhel.pool.ntp.org<br /> <br /> server 0.freebsd.pool.ntp.org iburst maxpoll 9<br /> server 1.freebsd.pool.ntp.org iburst maxpoll 9<br /> server 2.freebsd.pool.ntp.org iburst maxpoll 9<br /> <br /> server 0.ubuntu.pool.ntp.org<br /> server 1.ubuntu.pool.ntp.org<br /> server 2.ubuntu.pool.ntp.org<br /> server 3.ubuntu.pool.ntp.org<br /> <br /> server 0.debian.pool.ntp.org iburst dynamic<br /> server 1.debian.pool.ntp.org iburst dynamic<br /> server 2.debian.pool.ntp.org iburst dynamic<br /> server 3.debian.pool.ntp.org iburst dynamic<br /> <br /> &lt;/source&gt;<br /> <br /> 2) Restrict the type of access you allow these servers. In this example the servers are not allowed to modify the run-time configuration or query your Linux NTP server. <br /> &lt;source lang=bash&gt;<br /> restrict default ignore<br /> <br /> restrict otherntp.server.org mask 255.255.255.255 nomodify notrap noquery<br /> restrict ntp.research.gov mask 255.255.255.255 nomodify notrap noquery<br /> <br /> restrict -4 default kod notrap nomodify nopeer noquery<br /> restrict -6 default kod notrap nomodify nopeer noquery<br /> <br /> &lt;/source&gt;<br /> restrict default ignore will deny all access to any machine, server and client.<br /> <br /> The mask 255.255.255.255 statement is really a subnet mask limiting access to the single IP address of the remote NTP servers. <br /> <br /> 3) If this server is also going to provide time for other computers, such as PCs, other Linux servers and networking devices, then you'll have to define the networks from which this server will accept NTP synchronization requests. You do so with a modified restrict statement removing the noquery keyword to allow the network to query your NTP server. The syntax is: <br /> &lt;source lang=bash&gt;<br /> restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap<br /> &lt;/source&gt;<br /> In this case the mask statement has been expanded to include all 255 possible IP addresses on the local network. <br /> <br /> 4) We also want to make sure that localhost (the universal IP address used to refer to a Linux server itself) has full access without any restricting keywords: <br /> &lt;source lang=bash&gt;<br /> restrict 127.0.0.1<br /> &lt;/source&gt;<br /> 5) Save the file and restart NTP for these settings to take effect. You can now configure other Linux hosts on your network to synchronize with this new master NTP server in a similar fashion.<br /> <br /> =Get NTP Started =<br /> &lt;source lang=bash&gt;<br /> [root@bigboy tmp]# service ntpd start<br /> [root@bigboy tmp]# service ntpd stop<br /> [root@bigboy tmp]# service ntpd restart<br /> &lt;/source&gt;<br /> =Verifying NTP is Running =<br /> * Port 123<br /> * Protocol UDP<br /> &lt;source lang=bash&gt;<br /> [root@bigboy tmp]# pgrep ntpd<br /> 8038<br /> [root@cluster1 .ssh]# netstat -nutlp | grep ntpd<br /> udp 0 0 192.168.1.26:123 0.0.0.0:* 8038/ntpd <br /> udp 0 0 192.168.56.102:123 0.0.0.0:* 8038/ntpd <br /> udp 0 0 127.0.0.1:123 0.0.0.0:* 8038/ntpd <br /> udp 0 0 0.0.0.0:123 0.0.0.0:* 8038/ntpd <br /> <br /> &lt;/source&gt;<br /> <br /> =Doing An Initial Synchronization=<br /> If the time on the local server is very different from that of its primary time server your NTP daemon will eventually terminate itself leaving an error message in the /var/log/messages file. You should run the ntpdate -u command to force your server to become instantly synchronized with its NTP servers before starting the NTP daemon for the first time. The ntpdate command doesn't run continuously in the background, you will still have to run the ntpd daemon to get continuous NTP updates.<br /> <br /> Take a look at some sample output of the ntpdate command in which a server whose initial time was set to midnight, was correctly set to 8:03 am. <br /> &lt;source lang=bash&gt;<br /> [root@smallfry tmp]# date<br /> Thu Aug 12 00:00:00 PDT 2004<br /> [root@smallfry tmp]#<br /> &lt;/source&gt;<br /> The ntpdate command is run three times to synchronize smallfry's clock to server 192.168.1.100, but it must be run while the ntpd process is stopped. So you'll have to stop ntpd, run ntpdate and then start ntpd again. <br /> &lt;source lang=bash&gt;<br /> [root@smallfry tmp]# service ntpd stop<br /> [root@smallfry tmp]# ntpdate -u 192.168.1.100<br /> Looking for host 192.168.1.100 and service ntp<br /> host found : bigboy.my-site.com<br /> 12 Aug 08:03:38 ntpdate[2472]: step time server 192.168.1.100 offset 28993.084943 sec<br /> [root@smallfry tmp]# ntpdate -u 192.168.1.100<br /> Looking for host 192.168.1.100 and service ntp<br /> host found : bigboy.my-site.com<br /> 12 Aug 08:03:40 ntpdate[2472]: step time server 192.168.1.100 offset 2.467652 sec<br /> [root@smallfry tmp]# ntpdate -u 192.168.1.100<br /> Looking for host 192.168.1.100 and service ntp<br /> host found : bigboy.my-site.com<br /> 12 Aug 08:03:42 ntpdate[2472]: step time server 192.168.1.100 offset 0.084943 sec<br /> [root@smallfry tmp]# service ntpd start<br /> [root@smallfry tmp]#<br /> &lt;/source&gt;<br /> <br /> * The date is now corrected. <br /> &lt;source lang=bash&gt;<br /> [root@smallfry tmp]# date<br /> Thu Aug 12 08:03:45 PDT 2004<br /> [root@smallfry tmp]#<br /> &lt;/source&gt;<br /> =Determining If NTP Is Synchronized Properly=<br /> Use the ntpq command to see the servers with which you are synchronized. It provided you with a list of configured time servers and the delay, offset and jitter that your server is experiencing with them. For correct synchronization, the delay and offset values should be non-zero and the jitter value should be under 100. <br /> &lt;source lang=bash&gt;<br /> [root@cluster1 ~]# ntpq -p<br /> remote refid st t when poll reach delay offset jitter<br /> ==============================================================================<br /> rdns01.nexcess. 66.219.116.140 2 u 59 64 377 11.843 1434754 295744.<br /> tuppy.intrepidh 173.201.38.85 3 u 62 64 377 14.909 1658350 344907.<br /> elle.fallingsno 72.20.40.62 3 u 55 64 377 15.011 1439944 295244.<br /> *LOCAL(0) .LOCL. 10 l 54 64 377 0.000 0.000 0.001<br /> &lt;/source&gt;<br /> =Linux NTP clients cannot Synchronize Properly=<br /> A telltale sign that you haven't got proper synchronization is when all the remote servers have jitter, delay and reach values of 0. In some older versions of Fedora, the jitter values will be 4000. <br /> &lt;source lang=bash&gt;<br /> remote refid st t when poll reach delay offset jitter<br /> =============================================================================<br /> LOCAL(0) LOCAL(0) 10 l - 64 7 0.000 0.000 0.008<br /> ntp-cup.externa 0.0.0.0 16 u - 64 0 0.000 0.000 0.000<br /> snvl-smtp1.trim 0.0.0.0 16 u - 64 0 0.000 0.000 0.000<br /> nist1.aol-ca.tr 0.0.0.0 16 u - 64 0 0.000 0.000 0.000<br /> &lt;/source&gt;<br /> This could be caused by the following:<br /> <br /> * Older versions of the NTP package that don't work correctly if you use the DNS name for the NTP servers. In these cases you will want to use the actual IP addresses instead.<br /> * A firewall blocking access to your Stratum 1 and 2 NTP servers. This could be located on one of the networks between the NTP server and its time source, or firewall software such as iptables could be running on the server itself.<br /> * The notrust nomodify notrap keywords are present in the restrict statement for the NTP client. In some versions of the Fedora Core 2's implementation of NTP, clients will not be able to synchronize with a Fedora Core 2 time server unless the notrust nomodify notrap keywords are removed from the NTP client's restrict statement. <br /> <br /> * In this example the restrict statement has only the client network defined without any keywords and the configuration line that works with other NTP versions has been commented out: <br /> &lt;source lang=bash&gt;<br /> # -- CLIENT NETWORK -------<br /> #restrict 172.16.1.0 mask 255.255.255.0 notrust nomodify notrap<br /> restrict 172.16.1.0 mask 255.255.255.0<br /> &lt;/source&gt;<br /> =Fedora Core 2 File Permissions=<br /> All the Fedora/RedHat NTP daemons write temporary files to the /etc/ntp directory. Unfortunately, in Fedora Core 2, the permissions on this directory don't allow writing of temporary files. Instead you have to set the group and owner of the directory to be ntp. <br /> &lt;source lang=bash&gt;<br /> [root@bigboy tmp]# chown ntp:ntp /etc/ntp<br /> &lt;/source&gt;<br /> If you don't, you'll get errors like this in the /var/log/messages file. <br /> &lt;source lang=bash&gt;<br /> Aug 12 00:29:45 smallfry ntpd[2097]: can't open /etc/ntp/drift.TEMP: Permission denied<br /> &lt;/source&gt;<br /> <br /> =Time Not Syncing With Remote NTP Server=<br /> Some users have observed that their system time is being synchronized to the remote server's time when xntpd initially starts, but then is only being synchronized to their local time thereafter. An example /var/log/ntp or messages would look like this:<br /> &lt;source lang=bash&gt;<br /> 2 May 08:11:05 ntpd[2965]: synchronized to LOCAL(0), stratum 10<br /> 2 May 08:11:05 ntpd[2965]: kernel time sync disabled 0041<br /> 2 May 08:14:17 ntpd[2965]: synchronized to LOCAL(0), stratum 10<br /> 2 May 08:26:13 ntpd[2965]: kernel time sync enabled 0001<br /> 2 May 10:33:35 ntpd[3489]: synchronized to LOCAL(0), stratum 10<br /> 2 May 10:33:35 ntpd[3489]: kernel time sync disabled 0041<br /> <br /> # ntpq -p<br /> <br /> remote local st poll reach delay offset disp<br /> =======================================================================<br /> *LOCAL(0) 127.0.0.1 10 1024 377 0.00000 0.000000 0.11856<br /> =prv-time.provo. 137.65.211.18 2 1024 377 0.00041 -262.1380 0.11470<br /> &lt;/source&gt;<br /> <br /> The solution is to make NTP more persistent when probing the remote time server. This is done by appending the flags burst and iburst to the remote server; burst tells NTP to send a burst of eight packets to the remote server instead of one when the server is reachable, and iburst tells it to do the same when the server is not reachable. The result is faster and more reliable synchronizations.<br /> <br /> They can also be added directly to the server in /etc/ntp.conf as follows:<br /> <br /> * server 137.65.1.123 burst iburst<br /> =Check clock source=<br /> * cat /sys/devices/system/clocksource/clocksource0/available_clocksource<br /> tsc hpet acpi_pm jiffies<br /> * cat /sys/devices/system/clocksource/clocksource0/current_clocksource<br /> tsc<br /> tsc hpet acpi_pm jiffies<br /> <br /> if you have experience with lockups, you shall try to use 'clocksource=hpet' or 'clocksource=jiffies'. And 'nohz=off' too.<br /> <br /> in your grub.conf or /boot/grub/menu.lst file, you can set: <br /> * kernel /vmlinuz-2.6.XXXX root=XXXX clocksource=acpi_pm ro quiet splash<br /> <br /> * clocksource=[hpet|pit|tsc|acpi_pm|cyclone|scx200_hrt]<br /> <br /> =Kernel Time=<br /> To determine time you can use:<br /> &lt;source lang=bash&gt;<br /> [joseg@dev03 proc]$ dmesg | grep time.c<br /> time.c: Using 3.579545 MHz PM timer.<br /> time.c: Detected 2599.956 MHz processor.<br /> time.c: Using PM based timekeeping.<br /> [joseg@dev03 proc]$ <br /> <br /> [joseg@prod03 ~]$ cat /proc/cmdline<br /> ro root=LABEL=/ rhgb quiet nohpet nopmtimer console=tty0<br /> [joseg@prod03 ~] <br /> <br /> Taken from Documentation/kernel-parameters.txt<br /> <br /> clock= [BUGS=X86-32, HW] gettimeofday clocksource override.<br /> [Deprecated]<br /> Forces specified clocksource (if available) to be used<br /> when calculating gettimeofday(). If specified<br /> clocksource is not available, it defaults to PIT.<br /> Format: { pit | tsc | cyclone | pmtmr }<br /> <br /> clocksource= Override the default clocksource<br /> Format: &lt;string&gt;<br /> Override the default clocksource and use the clocksource<br /> with the name specified.<br /> Some clocksource names to choose from, depending on<br /> the platform:<br /> [all] jiffies (this is the base, fallback clocksource)<br /> [ACPI] acpi_pm<br /> [ARM] imx_timer1,OSTS,netx_timer,mpu_timer2,<br /> pxa_timer,timer3,32k_counter,timer0_1<br /> [AVR32] avr32<br /> [X86-32] pit,hpet,tsc;<br /> scx200_hrt on Geode; cyclone on IBM x440<br /> [MIPS] MIPS<br /> [PARISC] cr16<br /> [S390] tod<br /> [SH] SuperH<br /> [SPARC64] tick<br /> [X86-64] hpet,tsc<br /> <br /> &lt;/source&gt;<br /> <br /> * http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1006427<br /> [[Category:NTP]]</div>

Qais http://www.initq.com/index.php/Sysfs_and_procfs 2011-10-15T16:21:05Z

<p>Qais: </p> <hr /> <div>IIRC it was because /proc was meant to be to store process information but then turned into a maze of twisty directories with all sorts of random data dumped into it - including device information.<br /> <br /> Sysfs on the other hand is designed to be a representation of the kernel device model. For that reason stuff isn't just dumped in, the position of nodes with sysfs actually represents the hierachy of devices in relation to their subsytems.<br /> <br /> proc is the old one, it is more or less without rules and structure. And at some point it was decided that proc was a little to chaotic and a new way was needed.<br /> <br /> Then sysfs was created, and the new stuff that was added was put into sysfs like device information.<br /> <br /> So in some sense they do the same, but sysfs is a little bit more structured.<br /> <br /> Why are they made as file systems?<br /> <br /> Unix philosophy tells us that everything is a file, therefore it was created so it behaves as files.<br /> <br /> As I understand it, proc is just something to store the immediate info regarding the processes running in the system.<br /> <br /> Those parts has always been there and they will probably never move into sysfs.<br /> <br /> But there is more old stuff that you can find in proc, that has not been moved.<br /> <br /> [[Category:Linux Articles]]</div>

Qais http://www.initq.com/index.php/Udev 2011-10-15T15:40:16Z

<p>Qais: /* Not Enough Major/Minor Number Pairs */</p> <hr /> <div>Hotplugging (which is the word used to describe the process of inserting devices into a running system) is achieved in a Linux distribution by a combination of three components: Udev, HAL(Hardware Abstraction Layer), and Dbus.<br /> <br /> HAL (Hardware Abstraction Layer) is a daemon that allows desktop applications to readily access hardware information, to locate and use such hardware regardless of bus or device type. In this way a desktop GUI can present all resources to its user in a seamless and uniform manner. <br /> <br /> D-Bus is a message bus system that provides an easy way for inter-process communication. It consists of a daemon, which can be run both system-wide and for each user session, and a set of libraries to allow applications to use D-Bus. <br /> <br /> Udev supplies a dynamic device directory containing only the nodes for devices which are connected to the system. It creates or removes the device node files in the /dev directory as they are plugged in or taken out. Dbus is like a system bus which is used for inter-process communication. The HAL gets information from the Udev service, when a device is attached to the system and it creates an XML representation of that device. It then notifies the corresponding desktop application like Nautilus through the Dbus and Nautilus will open the mounted device files.<br /> <br /> =What is Udev?=<br /> Udev is the device manager for the Linux 2.6 kernel that creates/removes device nodes in the /dev directory dynamically. It is the successor of devfs and hotplug. It runs in userspace and the user can change device names using Udev rules.<br /> <br /> Udev depends on the sysfs file system which was introduced in the 2.5 kernel. It is sysfs which makes devices visible in user space. When a device is added or removed, kernel events are produced which will notify Udev in user space.<br /> <br /> The external binary /sbin/hotplug was used in earlier releases to inform Udev about device state change. That has been replaced and Udev can now directly listen to those events through Netlink.<br /> =Why Do We Need It ?=<br /> In the older kernels, the /dev directory contained statics device files. But with dynamic device creation, device nodes for only those devices which are actually present in the system are created. Let us see the disadvantages of the static /dev directory, which led to the development of Udev.<br /> =Problems Identifying the Exact Hardware Device for a Device Node in /dev=<br /> The kernel will assign a major/minor number pair when it detects a hardware device while booting the system. Let us consider two hard disks. The connection/alignment is in such a way that one is connected as a master and the other, as a slave. The Linux system will call them, /dev/hdaand /dev/hdb. Now, if we interchange the disks the device name will change. This makes it difficult to identify the correct device that is related to the available static device node. The condition gets worse when there are a bunch of hard disks connected to the system.<br /> <br /> Udev provides a persistent device naming system through the /dev directory, making it easier to identify the device.<br /> <br /> The following is an example of persistent symbolic links created by Udev for the hard disks attached to a system.<br /> &lt;source lang=bash&gt;<br /> $ ls -lR /dev/disk/<br /> /dev/disk/by-id:<br /> lrwxrwxrwx 1 root root 9 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593 -&gt; ../../sda <br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part1 -&gt; ../../sda1<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part2 -&gt; ../../sda2<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part3 -&gt; ../../sda3<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part4 -&gt; ../../sda4<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part5 -&gt; ../../sda5<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part6 -&gt; ../../sda6<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 scsi-SATA_WDC_WD800JD-75M_WD-WMAM9UT48593-part7 -&gt; ../../sda7<br /> /dev/disk/by-label:<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 1 -&gt; ../../sda6<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 boot1 -&gt; ../../sda2<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 project -&gt; ../../sda3<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 SWAP-sda7 -&gt; ../../sda7<br /> /dev/disk/by-path:<br /> lrwxrwxrwx 1 root root 9 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0 -&gt; ../../sda<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -&gt; ../../sda1<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -&gt; ../../sda2<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part3 -&gt; ../../sda3<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part4 -&gt; ../../sda4<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part5 -&gt; ../../sda5<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part6 -&gt; ../../sda6<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 pci-0000:00:1f.2-scsi-0:0:0:0-part7 -&gt; ../../sda7<br /> /dev/disk/by-uuid:<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 18283DC6283DA422 -&gt; ../../sda1<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 25a4068c-e84a-44ac-85e6-461b064d08cd -&gt; ../../sda6<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 3ea7cf15-511b-407a-a56b-c6bfa046fd9f -&gt; ../../sda5<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 8878a0a4-604e-4ddf-b62c-637c4fa84d3f -&gt; ../../sda2<br /> lrwxrwxrwx 1 root root 10 Jul 4 06:48 e50bcd6d-61ea-4b05-81a8-3cbe17ad6674 -&gt; ../../sda3<br /> &lt;/source&gt;<br /> Persistent device naming helps to identify the hardware device without much trouble.<br /> =Huge Number of Device Nodes in /dev=<br /> In the static model of device node creation, no method was available to identify the hardware devices actually present in the system. So, device nodes were created for all the devices that Linux was known to support at the time. The huge mess of device nodes in /dev made it difficult to identify the devices actually present in the system.<br /> =Not Enough Major/Minor Number Pairs=<br /> The number of static device nodes to be included increased a lot in recent times and the 8-bit scheme, that was used, proved to be insufficient for handling all the devices. As a result the major/minor number pairs started running out.<br /> <br /> Major number is the controller and minor number is the device attached to that controller. <br /> <br /> Character devices and block devices have a fixed major/minor number pair assigned to them. The authority responsible for assigning the major/minor pair is the Linux Assigned Name and Number Authority. But, a machine will not use all the available devices. So, there will be free major/minor numbers within a system. In such a situation, the kernel of that machine will borrow major/minor numbers from those free devices and assign those numbers to other devices which require it.<br /> <br /> This can create issues at times. The user space application which handles the device through the device node will not be aware of the number change. For the user space application, the device number assigned by LANANA is very important. So, the user space application should be informed about the major/minor number change. This is called dynamic assignment of major/minor numbers and Udev does this task.<br /> <br /> =Udev's Goals=<br /> * Run in user space.<br /> * Create persistent device names, take the device naming out of kernel space and implement rule based device naming.<br /> * Create a dynamic /dev with device nodes for devices present in the system and allocate major/minor numbers dynamically.<br /> * Provide a user space API to access the device information in the system.<br /> <br /> =Installation of Udev=<br /> Udev is the default device manager in the 2.6 kernel. Almost all modern Linux distributions come with Udev as part of the default installation. You can also get Udev from http://www.kernel.org/pub/linux/utils/kernel/hotplug/. The latest version of Udev needs the 2.6.25 kernel with sysfs, procfs, signalfd, inotify, Unix domain sockets, networking, and hotplug enabled.<br /> &lt;source lang=bash&gt;<br /> CONFIG_HOTPLUG=y<br /> CONFIG_UEVENT_HELPER_PATH=”&quot;<br /> CONFIG_NET=y<br /> CONFIG_UNIX=y<br /> CONFIG_SYSFS=y<br /> CONFIG_SYSFS_DEPRECATED*=n<br /> CONFIG_PROC_FS=y<br /> CONFIG_TMPFS=y<br /> CONFIG_TMPFS_POSIX_ACL=y <br /> CONFIG_INOTIFY=y<br /> CONFIG_SIGNALFD=y<br /> &lt;/source&gt;<br /> For a much more reliable operation, the kernel must not use the CONFIG_SYSFS_DEPRECATED* option.<br /> <br /> Udev depends on the proc and sys file systems and they must be mounted on /proc and /sys.<br /> =Working of Udev=<br /> The Udev daemon listens to the netlink socket that the kernel uses for communicating with user space applications. The kernel will send a bunch of data through the netlink socket when a device is added to, or removed from a system. The Udev daemon catches all this data and will do the rest, i.e., device node creation, module loading etc.<br /> =Kernel Device Event Management=<br /> * When bootup is initialized, the /dev directory is mounted in tmpfs.<br /> * After that, Udev will copy the static device nodes from /lib/udev/devices to the /dev directory.<br /> * The Udev daemon then runs and collects uevents from the kernel, for all the devices connected to the system.<br /> * The Udev daemon will parse the uevent data and it will match the data with the rules specified in /etc/udev/rules.d.<br /> * It will create the device nodes and symbolic links for the devices as specified in the rules.<br /> * The Udev daemon reads the rules from /etc/udev/rules.d/*.rules and stores them in the memory.<br /> * Udev will receive an inotify event, if any rules were changed. It will read the changes and will update the memory.<br /> <br /> /etc/udev/rules.s/11-automount-cds.rules<br /> &lt;source lang=bash&gt;<br /> KERNEL!=&quot;sr[0-9]*&quot;, GOTO=&quot;disc_by_label_auto_mount_end&quot;<br /> <br /> # Get label<br /> ACTION==&quot;add&quot;, PROGRAM==&quot;/sbin/blkid -o value -s LABEL %E{device}&quot;, ENV{dir_name}=&quot;%c&quot;<br /> <br /> ACTION==&quot;add&quot;, RUN+=&quot;/bin/mkdir -p '/media/%E{dir_name}'&quot;, RUN+=&quot;/bin/mount -o %E{mount_options} /dev/%k '/media/%E{dir_name}'&quot;<br /> ACTION==&quot;add&quot;, RUN+=&quot;/bin/ln -s /media/%E{dir_name} /media/disc&quot;<br /> ACTION==&quot;remove&quot;, RUN+=&quot;/bin/umount -l '/media/%E{dir_name}'&quot;, RUN+=&quot;/bin/rmdir '/media/%E{dir_name}'&quot;<br /> <br /> LABEL=&quot;disc_by_label_auto_mount_end&quot;<br /> <br /> KERNEL!=&quot;sr[0-9]*&quot;, GOTO=&quot;disc_by_label_auto_mount_end&quot;<br /> <br /> # Import FS infos<br /> IMPORT{program}=&quot;/sbin/blkid -o udev -p %N&quot;<br /> <br /> # Get a label if present, otherwise specify one<br /> ENV{ID_FS_LABEL}!=&quot;&quot;, ENV{dir_name}=&quot;%E{ID_FS_LABEL}&quot;<br /> ENV{ID_FS_LABEL}==&quot;&quot;, ENV{dir_name}=&quot;%k&quot;<br /> <br /> # Mount the device<br /> ACTION==&quot;add&quot;, RUN+=&quot;/bin/mkdir -p /media/%E{dir_name}&quot;, RUN+=&quot;/bin/mount /dev/%k /media/%E{dir_name}&quot;<br /> ACTION==&quot;add&quot;, RUN+=&quot;/bin/ln -s /media/%E{dir_name} /media/disc&quot;<br /> <br /> # Clean up after removal<br /> ACTION==&quot;remove&quot;, ENV{dir_name}!=&quot;&quot;, RUN+=&quot;/bin/umount -l /media/%E{dir_name}&quot;, RUN+=&quot;/bin/rmdir /media/%E{dir_name}&quot;<br /> <br /> # Exit<br /> &lt;/source&gt;<br /> <br /> =Device Driver Loading For Devices=<br /> Udev uses the modalias method to load device drivers. The modalias file located at/lib/modules/`uname -r`/modules.alias helps Udev to load the drivers. The modalias file is created by the depmod binary and it contains alternate names for the device drivers.<br /> <br /> Let us examine an example of device driver loading in Linux :<br /> <br /> I am using a C program to collect data from the netlink socket that Udev uses to create device nodes and load modules.<br /> &lt;source lang=bash&gt;<br /> [root@arch ~]# ./a.out<br /> add@/devices/pci0000:00/0000:00:02.1/usb1/1-4<br /> ACTION=add<br /> DEVPATH=/devices/pci0000:00/0000:00:02.1/usb1/1-4<br /> SUBSYSTEM=usb<br /> MAJOR=189<br /> MINOR=1<br /> DEVTYPE=usb_device<br /> DEVICE=/proc/bus/usb/001/002<br /> PRODUCT=1058/1010/105<br /> TYPE=0/0/0<br /> BUSNUM=001<br /> DEVNUM=002<br /> SEQNUM=1163<br /> add@/devices/pci0000:00/0000:00:02.1/usb1/1-4/1-4:1.0<br /> ACTION=add<br /> DEVPATH=/devices/pci0000:00/0000:00:02.1/usb1/1-4/1-4:1.0<br /> SUBSYSTEM=usb<br /> DEVTYPE=usb_interface<br /> DEVICE=/proc/bus/usb/001/002<br /> PRODUCT=1058/1010/105 …………………………………………<br /> &lt;/source&gt;<br /> You can see that it provides a lot of information about the device. This includes the modalias variable that tells Udev to load a particular module.<br /> <br /> The modalias data will look like :<br /> &lt;source lang=bash&gt;<br /> MODALIAS=pci:v000010ECd00008169sv00001385sd0000311Abc02sc00i00<br /> &lt;/source&gt;<br /> The modalias data contains all the information required to find the corresponding device driver :<br /> &lt;source lang=bash&gt;<br /> pci :- Its a pci device <br /> v :- vendor ID of the device. Here it is 000010EC ( ie 10EC )<br /> d :- device ID of the device. Here it is 00008169 ( ie : 8169 )<br /> sv and sd are subsystem versions for both vendor and device. <br /> &lt;/source&gt;<br /> The best place to find the vendor/product from the id of a PCI device is http://www.pcidatabase.com.<br /> <br /> Udev uses the modalias data to find the correct device driver from /lib/modules/`uname -r`/modules.alias.<br /> &lt;source lang=bash&gt;<br /> $ grep -i 10EC /lib/modules/`uname -r`/modules.alias | grep -i 8169<br /> alias pci:v000010ECd00008129sv*sd*bc*sc*i* r8169<br /> alias pci:v000010ECd00008169sv*sd*bc*sc*i* r8169<br /> &lt;/source&gt;<br /> You can see that the module which is suitable for the device is r8169. Let us get some more information about the driver.<br /> &lt;source lang=bash&gt;<br /> $ /sbin/modinfo r8169<br /> filename: /lib/modules/2.6.18-53.el5/kernel/drivers/net/r8169.ko<br /> version: 2.2LK-NAPI<br /> license: GPL<br /> description: RealTek RTL-8169 Gigabit Ethernet driver<br /> author: Realtek and the Linux r8169 crew <br /> srcversion: D5EDA4980B92CA2CF677B62<br /> alias: pci:v00001737d00001032sv*sd00000024bc*sc*i*<br /> alias: pci:v000016ECd00000116sv*sd*bc*sc*i*<br /> alias: pci:v00001186d00004300sv*sd*bc*sc*i*<br /> alias: pci:v000010ECd00008129sv*sd*bc*sc*i*<br /> alias: pci:v000010ECd00008169sv*sd*bc*sc*i*<br /> depends:<br /> vermagic: 2.6.18-53.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1<br /> parm: media:force phy operation. Deprecated by ethtool (8). (array of int)<br /> parm: rx_copybreak:Copy breakpoint for copy-only-tiny-frames (int)<br /> parm: use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)<br /> parm: debug:Debug verbosity level (0=none, …, 16=all) (int)<br /> &lt;/source&gt;<br /> Check out the line starting with “depends”. It describes the other modules which the r8169 module depends on. Udev will load these modules also.<br /> =Rule Processing and Device Node Creation=<br /> As already mentioned, Udev parses the rules in/etc/udev/rules.d/ for every device state change in the kernel. The Udev rule can be used to manipulate the device node name/permission/symlink in user space.<br /> <br /> Let us see some sample rules that will help you understand Udev rules better.<br /> <br /> The data supplied by the kernel through netlink is used by Udev to create the device nodes. The data includes the major/minor number pair and other device specific data such as device/vendor id, device serial number etc. The Udev rule can match all this data to change the name of the device node, create symbolic links or register the network link.<br /> <br /> The following example shows how to write a Udev rule to rename the network device in a system.<br /> <br /> We need to get the device information to create a rule.<br /> &lt;source lang=bash&gt;<br /> # udevadm info -a -p /sys/class/net/eth0/<br /> <br /> llooking at device '/devices/pci0000:00/0000:00:04.0/0000:01:06.0/net/eth0':<br /> KERNEL==”eth0″<br /> SUBSYSTEM==”net”<br /> DRIVER==”&quot;<br /> ATTR{addr_len}==”6″<br /> ATTR{dev_id}==”0×0″<br /> ATTR{ifalias}==”&quot;<br /> ATTR{iflink}==”3″<br /> ATTR{ifindex}==”3″<br /> ATTR{features}==”0×829″<br /> ATTR{type}==”1″<br /> ATTR{link_mode}==”0″<br /> ATTR{address}==”00:80:48:62:2a:33″<br /> ATTR{broadcast}==”ff:ff:ff:ff:ff:ff”<br /> ATTR{carrier}==”1″<br /> ATTR{dormant}==”0″<br /> ATTR{operstate}==”unknown”<br /> ATTR{mtu}==”1500″<br /> ATTR{flags}==”0×1003″<br /> ATTR{tx_queue_len}==”1000″<br /> looking at parent device ‘/devices/pci0000:00/0000:00:04.0/0000:01:06.0′:<br /> KERNELS==”0000:01:06.0″<br /> SUBSYSTEMS==”pci”<br /> DRIVERS==”8139too”<br /> ATTRS{vendor}==”0×10ec”<br /> ATTRS{device}==”0×8139″<br /> ATTRS{subsystem_vendor}==”0×10ec”<br /> ATTRS{subsystem_device}==”0×8139″<br /> ATTRS{class}==”0×020000″<br /> ATTRS{irq}==”19″<br /> ATTRS{local_cpus}==”ff”<br /> ATTRS{local_cpulist}==”0-7″<br /> ATTRS{modalias}==”pci:v000010ECd00008139sv000010ECsd00008139bc02sc00i00″<br /> ATTRS{enable}==”1″<br /> ATTRS{broken_parity_status}==”0″<br /> ATTRS{msi_bus}==”&quot;<br /> looking at parent device ‘/devices/pci0000:00/0000:00:04.0′:<br /> KERNELS==”0000:00:04.0″<br /> SUBSYSTEMS==”pci”<br /> DRIVERS==”&quot;<br /> ATTRS{vendor}==”0×10de”<br /> ATTRS{device}==”0×03f3″<br /> ATTRS{subsystem_vendor}==”0×0000″<br /> ATTRS{subsystem_device}==”0×0000″<br /> ATTRS{class}==”0×060401″<br /> ATTRS{irq}==”0″<br /> ATTRS{local_cpus}==”ff”<br /> ATTRS{local_cpulist}==”0-7″<br /> ATTRS{modalias}==”pci:v000010DEd000003F3sv00000000sd00000000bc06sc04i01″<br /> ATTRS{enable}==”1″<br /> ATTRS{broken_parity_status}==”0″<br /> ATTRS{msi_bus}==”1″<br /> looking at parent device ‘/devices/pci0000:00′:<br /> KERNELS==”pci0000:00″<br /> SUBSYSTEMS==”&quot;<br /> DRIVERS==”&quot;<br /> &lt;/source&gt;<br /> You can see that Udev has a lot of information about the network device. Let us examine it in detail :<br /> &lt;source lang=bash&gt;<br /> KERNEL==&quot;eth0&quot; :- kernel name of the device is eth0<br /> DRIVERS==”8139too” :- driver loaded is 8139too<br /> ATTR{address}==”00:80:48:62:2a:33″ :- hardware address of the device<br /> ATTRS{vendor}==”0×10ec” :- vendor id<br /> ATTRS{device}==”0×8139″ :- device id<br /> &lt;/source&gt;<br /> Let us create a rule to rename this network device to eth1 (This name will be persistent and will not be reset after a reboot).<br /> &lt;source lang=bash&gt;<br /> [root@arch ~]# cat /etc/udev/rules.d/70-persistent-net.rules<br /> SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:80:48:62:2a:33″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth1″<br /> &lt;/source&gt;<br /> This rule renames the device to eth1. We can easily manage the network and other device nodes in the system, this way.<br /> =Udev Utilities=<br /> Udev provides some user space utilities to manage devices and device nodes in a system. One such command that you will find in all of the latest Linux distributions is ‘udevadm’. The udevadm command is functionally capable of doing all the tasks which were done by the separate commands shown above.<br /> <br /> This utility can be used to regenerate the device nodes in a running system as shown:<br /> &lt;source lang=bash&gt;<br /> [root@arch ~]# ls -l /dev/ | wc -l<br /> 150<br /> [root@arch ~]# rm -rf /dev/*<br /> rm: cannot remove `/dev/pts/0′: Operation not permitted<br /> rm: cannot remove directory `/dev/shm’: Device or resource busy<br /> [root@arch ~]# ls -l /dev/ | wc -l<br /> 4<br /> [root@arch ~]# udevadm trigger<br /> [root@arch ~]# ls -l /dev/ | wc -l<br /> 150<br /> &lt;/source&gt;<br /> There are many other useful operations that can be done using the udevadm command. You can get more information from the man page of udevadm.<br /> =What is the Future of Udev ?=<br /> It is impossible to predict the future of a Linux sub system. Linux is undergoing rapid development and it is probably not wise to predict the future of the Linux kernel. The DEVfs system which was introduced as a solution to static device nodes disappeared within a short span of time. But Udev has proven to be a successful device manager for the modern Linux kernel, and promises to be a more stable, feature rich device management system in future releases.<br /> <br /> [[Category:Linux Articles]]</div>

Qais http://www.initq.com/index.php/Setting_up_Bind 2011-10-06T21:00:10Z

<p>Qais: /* Complete Zone Datafiles */</p> <hr /> <div>We will make a movie dns. <br /> <br /> =db.DOMAIN=<br /> File that maps hostnames to addresses is called db.domian. We will call ours db.movie.edu.<br /> <br /> =db.ADDR=<br /> The files mapping addresses to hostnames are called db.ADDR, where ADDR is the network number without training zeros. In our example these files will be db.192.249.249 and db.192.253.253<br /> <br /> The db.domain and db.addr are called zone datafiles. The format of these files is called master file format.<br /> <br /> =db.cache=<br /> <br /> =db.127.0.0=<br /> <br /> The db.cache and db.127.0.0 files are called overhead.<br /> <br /> To tie all these files together you need a named.conf file.<br /> <br /> =Zone DataFiles=<br /> <br /> * TTL<br /> * SOA record (start of authority for this zone)<br /> * NS record (lists a nameserver for this zone)<br /> * Other records (data about hosts in this zone)<br /> * A (name-to-address mapping)<br /> * PTR (name-to-address mapping)<br /> * CNAME (canonical name of aliases)<br /> comments start with a semicolon.<br /> ==Setting the zone default TTL==<br /> We add the following resource record to db.movie.edu file.<br /> <br /> $TTL 3h<br /> <br /> ==SOA Records==<br /> We add the following resource record to db.movie.edu file.<br /> &lt;source lang=bash&gt;<br /> movie.edu. IN SOA toystory.movie.edu. al.movie.edu. (<br /> 1 ; Serial<br /> 3h ; Refresh after 3 hours<br /> 1h ; Retry after 1 hour<br /> 1w ; Expire after 1 week<br /> 1h ) ; Negative caching TTL of 1 hour<br /> &lt;/source&gt;<br /> <br /> ==NS Records==<br /> Here is the information about our two name servers. We add the following resource record to db.movie.edu file.<br /> &lt;source lang=bash&gt;<br /> ; NS Record<br /> movie.edu. IN NS toystory.movie.edu.<br /> movie.edu. IN NS wormhole.movie.edu.<br /> &lt;/source&gt;<br /> <br /> ==Address and Alias Records==<br /> Next, we create name-to-address mappings. We add the following resource record to db.movie.edu file.<br /> &lt;source lang=bash&gt;<br /> ;<br /> ; Host addresses<br /> ;<br /> localhost.movie.edu. IN A 127.0.0.1<br /> shrek.movie.edu. IN A 192.249.249.2<br /> toystory.movie.edu. IN A 192.249.249.3<br /> monsters-inc.movie.edu. IN A 192.249.249.4<br /> misery.movie.edu. IN A 192.253.253.2<br /> ;<br /> ; Multi-homes hosts<br /> ;<br /> wormhole.movie.edu. IN A 192.249.249.1<br /> wormhole.movie.edu. IN A 192.253.253.1<br /> ;<br /> ; Aliases<br /> ;<br /> toys.movie.edu. IN CNAME toystory.movie.edu.<br /> mi.movie.edu. IN CNAME monsters-inc.movie.edu.<br /> wh.movie.edu. IN CNAME wormhole.movie.edu.<br /> wh249.movie.edu. IN A 192.249.249.1<br /> wh253.movie.edu. IN A 192.253.253.1<br /> <br /> &lt;/source&gt;<br /> <br /> The A stands for addresses. wormhole.movie.edu is a multihomed host. It has two addresses associated with it. CNAME is canonical name resource record. The last two entries solve a problem to check individual interface for the multihomed host.<br /> <br /> ==PTR Records==<br /> Next we create address-to-name mappings. This will go in the file 192.249.249<br /> <br /> &lt;source lang=bash&gt;<br /> 1.249.249.192.in-addr.arpa. IN PTR wormhole.movie.edu.<br /> 2.249.249.192.in-addr.arpa. IN PTR shrek.movie.edu.<br /> 3.249.249.192.in-addr.arpa. IN PTR toystory.movie.edu.<br /> 4.249.249.192.in-addr.arpa. IN PTR monsters-inc.movie.edu.<br /> &lt;/source&gt;<br /> <br /> Same data is inserted for file db.192.253.253<br /> &lt;source lang=bash&gt;<br /> 1.249.249.192.in-addr.arpa. IN PTR wormhole.movie.edu.<br /> 2.249.249.192.in-addr.arpa. IN PTR shrek.movie.edu.<br /> 3.249.249.192.in-addr.arpa. IN PTR toystory.movie.edu.<br /> 4.249.249.192.in-addr.arpa. IN PTR monsters-inc.movie.edu.<br /> &lt;/source&gt;<br /> <br /> =Complete Zone Datafiles=<br /> Here is the complete db.movie.edu:<br /> &lt;source lang=bash&gt;<br /> $TTL 3h<br /> movie.edu. IN SOA toystory.movie.edu. al.movie.edu. (<br /> 1 ; Serial<br /> 3h ; Refresh after 3 hours<br /> 1h ; Retry after 1 hour<br /> 1w ; Expire after 1 week<br /> 1h ) ; Negative caching TTL of 1 hour<br /> <br /> ; NS Record<br /> movie.edu. IN NS toystory.movie.edu.<br /> movie.edu. IN NS wormhole.movie.edu.<br /> <br /> ;<br /> ; Host addresses<br /> ;<br /> localhost.movie.edu. IN A 127.0.0.1<br /> shrek.movie.edu. IN A 192.249.249.2<br /> toystory.movie.edu. IN A 192.249.249.3<br /> monsters-inc.movie.edu. IN A 192.249.249.4<br /> misery.movie.edu. IN A 192.253.253.2<br /> ;<br /> ; Multi-homes hosts<br /> ;<br /> wormhole.movie.edu. IN A 192.249.249.1<br /> wormhole.movie.edu. IN A 192.253.253.1<br /> ;<br /> ; Aliases<br /> ;<br /> toys.movie.edu. IN CNAME toystory.movie.edu.<br /> mi.movie.edu. IN CNAME monsters-inc.movie.edu.<br /> wh.movie.edu. IN CNAME wormhole.movie.edu.<br /> <br /> ; Interface specific names<br /> <br /> wh249.movie.edu. IN A 192.249.249.1<br /> wh253.movie.edu. IN A 192.253.253.1<br /> &lt;/source&gt;<br /> <br /> =Complete PTR files=<br /> db.192.249.249<br /> &lt;source lang=bash&gt;<br /> $TTL 3h<br /> 249.249.192.in-addr.arpa. IN SOA toystory.movie.edu. al.movie.edu. (<br /> 1 ; Serial<br /> 3h ; Refresh after 3 hours<br /> 1h ; Retry after 1 hour<br /> 1w ; Expire after 1 week<br /> 1h ) ; Negative caching TTL of 1 hour<br /> <br /> &lt;/source&gt;<br /> db.192.253.253<br /> &lt;source lang=bash&gt;<br /> $TTL 3h<br /> 253.253.192.in-addr.arpa. IN SOA toystory.movie.edu. al.movie.edu. (<br /> 1 ; Serial<br /> 3h ; Refresh after 3 hours<br /> 1h ; Retry after 1 hour<br /> 1w ; Expire after 1 week<br /> 1h ) ; Negative caching TTL of 1 hour<br /> <br /> &lt;/source&gt;<br /> [[Category:DNS]]</div>

Qais http://www.initq.com/index.php/Ports_on_Linux 2011-10-06T16:43:45Z

<p>Qais: </p> <hr /> <div>&lt;source lang=bash&gt;<br /> Port # / Layer Name Comment<br /> 1 tcpmux TCP port service multiplexer<br /> 5 rje Remote Job Entry<br /> 7 echo Echo service<br /> 9 discard Null service for connection testing<br /> 11 systat System Status service for listing connected ports<br /> 13 daytime Sends date and time to requesting host<br /> 17 qotd Sends quote of the day to connected host<br /> 18 msp Message Send Protocol<br /> 19 chargen Character Generation service; sends endless stream of characters<br /> 20 ftp-data FTP data port<br /> 21 ftp File Transfer Protocol (FTP) port; sometimes used by File Service Protocol (FSP)<br /> 22 ssh Secure Shell (SSH) service<br /> 23 telnet The Telnet service<br /> 25 smtp Simple Mail Transfer Protocol (SMTP)<br /> 37 time Time Protocol<br /> 39 rlp Resource Location Protocol<br /> 42 nameserver Internet Name Service<br /> 43 nicname WHOIS directory service<br /> 49 tacacs Terminal Access Controller Access Control System for TCP/IP based authentication and access<br /> 50 re-mail-ck Remote Mail Checking Protocol<br /> 53 domain domain name services (such as BIND)<br /> 63 whois++ WHOIS++, extended WHOIS services<br /> 67 bootps Bootstrap Protocol (BOOTP) services; also used by Dynamic Host Configuration Protocol (DHCP) services<br /> 68 bootpc Bootstrap (BOOTP) client; also used by Dynamic Host Control Protocol (DHCP) clients<br /> 69 tftp Trivial File Transfer Protocol (TFTP)<br /> 70 gopher Gopher Internet document search and retrieval<br /> 71 netrjs-1 Remote Job Service<br /> 72 netrjs-2 Remote Job Service<br /> 73 netrjs-3 Remote Job Service<br /> 73 netrjs-4 Remote Job Service<br /> 79 finger Finger service for user contact information<br /> 80 http HyperText Transfer Protocol (HTTP) for World Wide Web (WWW) services<br /> 88 kerberos Kerberos network authentication system<br /> 95 supdup Telnet protocol extension<br /> 101 hostname Hostname services on SRI-NIC machines<br /> 102 iso-tsap ISO Development Environment (ISODE) network applications<br /> 105 csnet-ns Mailbox nameserver; also used by CSO nameserver<br /> 107 rtelnet Remote Telnet<br /> 109 pop2 Post Office Protocol version 2<br /> 110 pop3 Post Office Protocol version 3<br /> 111 sunrpc Remote Procedure Call (RPC) Protocol for remote command execution, used by Network Filesystem (NFS)<br /> 113 auth Authentication and Ident protocols<br /> 115 sftp Secure File Transfer Protocol (SFTP) services<br /> 117 uucp-path Unix-to-Unix Copy Protocol (UUCP) Path services<br /> 119 nntp Network News Transfer Protocol (NNTP) for the USENET discussion system<br /> 123 ntp Network Time Protocol (NTP)<br /> 137 netbios-ns NETBIOS Name Services used in Red Hat Enterprise Linux by Samba<br /> 138 netbios-dgm NETBIOS Datagram Services used in Red Hat Enterprise Linux by Samba<br /> 139 netbios-ssn NETBIOS Session Services used in Red Hat Enterprise Linux by Samba<br /> 143 imap Internet Message Access Protocol (IMAP)<br /> 161 snmp Simple Network Management Protocol (SNMP)<br /> 162 snmptrap Traps for SNMP<br /> 163 cmip-man Common Management Information Protocol (CMIP)<br /> 164 cmip-agent Common Management Information Protocol (CMIP)<br /> 174 mailq MAILQ<br /> 177 xdmcp X Display Manager Control Protocol<br /> 178 nextstep NeXTStep window server<br /> 179 bgp Border Gateway Protocol<br /> 191 prospero Cliffod Neuman's Prospero services<br /> 194 irc Internet Relay Chat (IRC)<br /> 199 smux SNMP UNIX Multiplexer<br /> 201 at-rtmp AppleTalk routing<br /> 202 at-nbp AppleTalk name binding<br /> 204 at-echo AppleTalk echo<br /> 206 at-zis AppleTalk zone information<br /> 209 qmtp Quick Mail Transfer Protocol (QMTP)<br /> 210 z39.50 NISO Z39.50 database<br /> 213 ipx Internetwork Packet Exchange (IPX), a datagram protocol commonly used in Novell Netware environments<br /> 220 imap3 Internet Message Access Protocol version 3<br /> 245 link LINK<br /> 347 fatserv Fatmen Server<br /> 363 rsvp_tunnel RSVP Tunnel<br /> 369 rpc2portmap Coda filesystem portmapper<br /> 370 codaauth2 Coda filesystem authentication services<br /> 372 ulistproc UNIX Listserv<br /> 389 ldap Lightweight Directory Access Protocol (LDAP)<br /> 427 svrloc Service Location Protocol (SLP)<br /> 434 mobileip-agent Mobile Internet Protocol (IP) agent<br /> 435 mobilip-mn Mobile Internet Protocol (IP) manager<br /> 443 https Secure Hypertext Transfer Protocol (HTTP)<br /> 444 snpp Simple Network Paging Protocol<br /> 445 microsoft-ds Server Message Block (SMB) over TCP/IP<br /> 464 kpasswd Kerberos password and key changing services<br /> 468 photuris Photuris session key management protocol<br /> 487 saft Simple Asynchronous File Transfer (SAFT) protocol<br /> 488 gss-http Generic Security Services (GSS) for HTTP<br /> 496 pim-rp-disc Rendezvous Point Discovery (RP-DISC) for Protocol Independent Multicast (PIM) services<br /> 500 isakmp Internet Security Association and Key Management Protocol (ISAKMP)<br /> 535 iiop Internet Inter-Orb Protocol (IIOP)<br /> 538 gdomap GNUstep Distributed Objects Mapper (GDOMAP)<br /> 546 dhcpv6-client Dynamic Host Configuration Protocol (DHCP) version 6 client<br /> 547 dhcpv6-server Dynamic Host Configuration Protocol (DHCP) version 6 Service<br /> 554 rtsp Real Time Stream Control Protocol (RTSP)<br /> 563 nntps Network News Transport Protocol over Secure Sockets Layer (NNTPS)<br /> 565 whoami whoami<br /> 587 submission Mail Message Submission Agent (MSA)<br /> 610 npmp-local Network Peripheral Management Protocol (NPMP) local / Distributed Queueing System (DQS)<br /> 611 npmp-gui Network Peripheral Management Protocol (NPMP) GUI / Distributed Queueing System (DQS)<br /> 612 hmmp-ind HMMP Indication / DQS<br /> 631 ipp Internet Printing Protocol (IPP)<br /> 636 ldaps Lightweight Directory Access Protocol over Secure Sockets Layer (LDAPS)<br /> 674 acap Application Configuration Access Protocol (ACAP)<br /> 694 ha-cluster Heartbeat services for High-Availability Clusters<br /> 749 kerberos-adm Kerberos version 5 (v5) 'kadmin' database administration<br /> 750 kerberos-iv Kerberos version 4 (v4) services<br /> 765 webster Network Dictionary<br /> 767 phonebook Network Phonebook<br /> 873 rsync rsync file transfer services<br /> 992 telnets Telnet over Secure Sockets Layer (TelnetS)<br /> 993 imaps Internet Message Access Protocol over Secure Sockets Layer (IMAPS)<br /> 994 ircs Internet Relay Chat over Secure Sockets Layer (IRCS)<br /> 995 pop3s Post Office Protocol version 3 over Secure Sockets Layer (POP3S)<br /> <br /> Table C-1. Well Known Ports<br /> <br /> The following ports are UNIX-specific and cover services ranging from email to authentication and more. Names enclosed in brackets (for example, [service]) are either daemon names for the service or common alias(es).<br /> Port # / Layer Name Comment<br /> 512/tcp exec Authentication for remote process execution<br /> 512/udp biff [comsat] Asynchrous mail client (biff) and service (comsat)<br /> 513/tcp login Remote Login (rlogin)<br /> 513/udp who [whod] who logged user listing<br /> 514/tcp shell [cmd] remote shell (rshell) and remote copy (rcp) with no logging<br /> 514/udp syslog UNIX system logging service<br /> 515 printer [spooler] line printer (lpr) spooler<br /> 517/udp talk talk remote calling service and client<br /> 518/udp ntalk Network talk (ntalk) remote calling service and client<br /> 519 utime [unixtime] UNIX time (utime) protocol<br /> 520/tcp efs Extended Filename Server (EFS)<br /> 520/udp router [route, routed] Routing Information Protocol (RIP)<br /> 521 ripng Routing Information Protocol for Internet Protocol version 6 (IPv6)<br /> 525 timed [timeserver] Time daemon (timed)<br /> 526/tcp tempo [newdate] Tempo<br /> 530/tcp courier [rpc] Courier Remote Procedure Call (RPC) protocol<br /> 531/tcp conference [chat] Internet Relay Chat<br /> 532 netnews Netnews<br /> 533/udp netwall Netwall for emergency broadcasts<br /> 540/tcp uucp [uucpd] Unix-to-Unix copy services<br /> 543/tcp klogin Kerberos version 5 (v5) remote login<br /> 544/tcp kshell Kerberos version 5 (v5) remote shell<br /> 548 afpovertcp Appletalk Filing Protocol (AFP) over Transmission Control Protocol (TCP)<br /> 556 remotefs [rfs_server, rfs] Brunhoff's Remote Filesystem (RFS)<br /> <br /> Table C-2. UNIX Specific Ports<br /> <br /> Table C-3 lists ports submitted by the network and software community to the IANA for formal registration in the port number list.<br /> Port # / Layer Name Comment<br /> 1080 socks SOCKS network application proxy services<br /> 1236 bvcontrol [rmtcfg] Garcilis Packeten Remote Configuration Server[a]<br /> 1300 h323hostcallsc H.323 teleconferencing Host Call Secure<br /> 1433 ms-sql-s Microsoft SQL Server<br /> 1434 ms-sql-m Microsoft SQL Monitor<br /> 1494 ica Citrix ICA Client<br /> 1512 wins Microsoft Windows Internet Name Server<br /> 1524 ingreslock Ingres Database Management System (DBMS) lock services<br /> 1525 prospero-np Prospero non-priveleged<br /> 1645 datametrics [old-radius] Datametrics / old radius entry<br /> 1646 sa-msg-port [oldradacct] sa-msg-port / old radacct entry<br /> 1649 kermit Kermit file transfer and management service<br /> 1701 l2tp [l2f] Layer 2 Tunneling Protocol (LT2P) / layer 2 forwarding (L2F)<br /> 1718 h323gatedisc H.323 telecommunication Gatekeeper Discovery<br /> 1719 h323gatestat H.323 telecommunication Gatekeeper Status<br /> 1720 h323hostcall H.323 telecommunication Host Call setup<br /> 1758 tftp-mcast Trivial FTP Multicast<br /> 1759 mtftp Multicast Trivial FTP (MTFTP)<br /> 1789 hello Hello router communication protocol<br /> 1812 radius Radius dial-up authentication and accounting services<br /> 1813 radius-acct Radius Accounting<br /> 1911 mtp Starlight Networks Multimedia Transport Protocol (MTP)<br /> 1985 hsrp Cisco Hot Standby Router Protocol<br /> 1986 licensedaemon Cisco License Management Daemon<br /> 1997 gdp-port Cisco Gateway Discovery Protocol (GDP)<br /> 2049 nfs [nfsd] Network File System (NFS)<br /> 2102 zephyr-srv Zephyr notice transport and delivery Server<br /> 2103 zephyr-clt Zephyr serv-hm connection<br /> 2104 zephyr-hm Zephyr host manager<br /> 2401 cvspserver Concurrent Versions System (CVS) client/server operations<br /> 2430/tcp venus Venus cache manager for Coda file system (codacon port)<br /> 2430/udp venus Venus cache manager for Coda file system (callback/wbc interface)<br /> 2431/tcp venus-se Venus Transmission Control Protocol (TCP) side effects<br /> 2431/udp venus-se Venus User Datagram Protocol (UDP) side effects<br /> 2432/udp codasrv Coda file system server port<br /> 2433/tcp codasrv-se Coda file system TCP side effects<br /> 2433/udp codasrv-se Coda file system UDP SFTP side effect<br /> 2600 hpstgmgr [zebrasrv] HPSTGMGR; Zebra routing[b]<br /> 2601 discp-client [zebra] discp client; Zebra integrated shell<br /> 2602 discp-server [ripd] discp server; Routing Information Protocol daemon (ripd)<br /> 2603 servicemeter [ripngd] Service Meter; RIP daemon for IPv6<br /> 2604 nsc-ccs [ospfd] NSC CCS; Open Shortest Path First daemon (ospfd)<br /> 2605 nsc-posa NSC POSA; Border Gateway Protocol daemon (bgpd)<br /> 2606 netmon [ospf6d] Dell Netmon; OSPF for IPv6 daemon (ospf6d)<br /> 2809 corbaloc Common Object Request Broker Architecture (CORBA) naming service locator<br /> 3130 icpv2 Internet Cache Protocol version 2 (v2); used by Squid Proxy caching server<br /> 3306 mysql MySQL database service<br /> 3346 trnsprntproxy Trnsprnt Proxy<br /> 4011 pxe Pre-execution Environment (PXE) service<br /> 4321 rwhois Remote Whois (rwhois) service<br /> 4444 krb524 Kerberos version 5 (v5) to version 4 (v4) ticket translator<br /> 5002 rfe Radio Free Ethernet (RFE) audio broadcasting system<br /> 5308 cfengine Configuration Engine (Cfengine)<br /> 5999 cvsup [CVSup] CVSup file transfer and update tool<br /> 6000 x11 [X] X Window System services<br /> 7000 afs3-fileserver Andrew File System (AFS) file server<br /> 7001 afs3-callback AFS port for callbacks to cache manager<br /> 7002 afs3-prserver AFS user and group database<br /> 7003 afs3-vlserver AFS volume location database<br /> 7004 afs3-kaserver AFS Kerberos authentication service<br /> 7005 afs3-volser AFS volume management server<br /> 7006 afs3-errors AFS error interpretation service<br /> 7007 afs3-bos AFS basic overseer process<br /> 7008 afs3-update AFS server-to-server updater<br /> 7009 afs3-rmtsys AFS remote cache manager service<br /> 9876 sd Session Director<br /> 10080 amanda Advanced Maryland Automatic Network Disk Archiver (Amanda) backup services<br /> 11371 pgpkeyserver Pretty Good Privacy (PGP) / GNU Privacy Guard (GPG) public keyserver<br /> 11720 h323callsigalt H.323 Call Signal Alternate<br /> 13720 bprd Veritas NetBackup Request Daemon (bprd)<br /> 13721 bpdbm Veritas NetBackup Database Manager (bpdbm)<br /> 13722 bpjava-msvc Veritas NetBackup Java / Microsoft Visual C++ (MSVC) Protocol<br /> 13724 vnetd Veritas Network Utility<br /> 13782 bpcd Vertias NetBackup<br /> 13783 vopied Veritas VOPIED Protocol<br /> 22273 wnn6 [wnn4] Kana/Kanji conversion system[c]<br /> 26000 quake Quake (and related) multi-player game servers<br /> 26208 wnn6-ds <br /> 33434 traceroute Traceroute network tracking tool<br /> Notes:<br /> a. Comment from /etc/services: &quot;Port 1236 is registered as `bvcontrol', but is also used by the Gracilis Packeten remote config server. The official name is listed as the primary name, with the unregistered name as an alias.&quot;<br /> b. Note from /etc/services: &quot;Ports numbered 2600 through 2606 are used by the zebra package without being registered. The primary names are the registered names, and the unregistered names used by zebra are listed as aliases.&quot;<br /> c. Note from /etc/services: &quot;This port is registered as wnn6, but also used under the unregistered name 'wnn4' by the FreeWnn package.&quot;<br /> <br /> Table C-3. Registered Ports<br /> <br /> Table C-4 shows a list of ports related to Datagram Delivery Protocol (DDP) used on AppleTalk networks.<br /> Port # / Layer Name Comment<br /> 1/ddp rtmp Routing Table Management Protocol<br /> 2/ddp nbp Name Binding Protocol<br /> 4/ddp echo AppleTalk Echo Protocol<br /> 6/ddp zip Zone Information Protocol<br /> <br /> Table C-4. Datagram Deliver Protocol Ports<br /> <br /> Table C-5 is a listing of ports related to the Kerberos network authentication protocol. Where noted, v5 refers to Kerberos version 5 protocol. Note that these ports are not registered with the IANA.<br /> Port # / Layer Name Comment<br /> 751 kerberos_master Kerberos authentication<br /> 752 passwd_server Kerberos Password (kpasswd) server<br /> 754 krb5_prop Kerberos v5 slave propagation<br /> 760 krbupdate [kreg] Kerberos registration<br /> 1109 kpop Kerberos Post Office Protocol (KPOP)<br /> 2053 knetd Kerberos de-multiplexor<br /> 2105 eklogin Kerberos v5 encrypted remote login (rlogin)<br /> <br /> Table C-5. Kerberos (Project Athena/MIT) Ports<br /> <br /> Table C-6 is a listing of unregistered ports that are used by services and protocols that may be installed on your Red Hat Enterprise Linux system or is necessary for communication between Red Hat Enterprise Linux and systems running other operating systems.<br /> Port # / Layer Name Comment<br /> 15/tcp netstat Network Status (netstat)<br /> 98/tcp linuxconf Linuxconf Linux administration tool<br /> 106 poppassd Post Office Protocol Password change daemon (POPPASSD)<br /> 465/tcp smtps Simple Mail Transfer Protocol over Secure Sockets Layer (SMTPS)<br /> 616/tcp gii Gated (routing daemon) Interactive Interface<br /> 808 omirr [omirrd] Online Mirror (Omirr) file mirroring services<br /> 871/tcp supfileserv Software Upgrade Protocol (SUP) server<br /> 901/tcp swat Samba Web Administration Tool (SWAT)<br /> 953 rndc Berkeley Internet Name Domain version 9 (BIND 9) remote name daemon configuration tool<br /> 1127 sufiledbg Software Upgrade Protocol (SUP) debugging<br /> 1178/tcp skkserv Simple Kana to Kanji (SKK) Japanese input server<br /> 1313/tcp xtel French Minitel text information system<br /> 1529/tcp support [prmsd, gnatsd] GNATS bug tracking system<br /> 2003/tcp cfinger GNU Finger<br /> 2150 ninstall Network Installation Service<br /> 2988 afbackup afbackup client-server backup system<br /> 3128/tcp squid Squid Web proxy cache<br /> 3455 prsvp RSVP port<br /> 5432 postgres PostgreSQL database<br /> 4557/tcp fax FAX transmission service (old service)<br /> 4559/tcp hylafax HylaFAX client-server protocol (new service)<br /> 5232 sgi-dgl SGI Distributed Graphics Library<br /> 5354 noclog NOCOL network operation center logging daemon (noclogd)<br /> 5355 hostmon NOCOL network operation center host monitoring<br /> 5680/tcp canna Canna Japanese character input interface<br /> 6010/tcp x11-ssh-offset Secure Shell (SSH) X11 forwarding offset<br /> 6667 ircd Internet Relay Chat daemon (ircd)<br /> 7100/tcp xfs X Font Server (XFS)<br /> 7666/tcp tircproxy Tircproxy IRC proxy service<br /> 8008 http-alt Hypertext Tranfer Protocol (HTTP) alternate<br /> 8080 webcache World Wide Web (WWW) caching service<br /> 8081 tproxy Transparent Proxy<br /> 9100/tcp jetdirect [laserjet, hplj] Hewlett-Packard (HP) JetDirect network printing service<br /> 9359 mandelspawn [mandelbrot] Parallel Mandelbrot spawning program for the X Window System<br /> 10081 kamanda Amanda backup service over Kerberos<br /> 10082/tcp amandaidx Amanda backup services<br /> 10083/tcp amidxtape Amanda backup services<br /> 20011 isdnlog Integrated Systems Digital Network (ISDN) logging system<br /> 20012 vboxd ISDN voice box daemon (vboxd)<br /> 22305/tcp wnn4_Kr kWnn Korean input system<br /> 22289/tcp wnn4_Cn cWnn Chinese input system<br /> 22321/tcp wnn4_Tw tWnn Chinese input system (Taiwan)<br /> 24554 binkp Binkley TCP/IP Fidonet mailer daemon<br /> 27374 asp Address Search Protocol<br /> 60177 tfido Ifmail FidoNet compatible mailer service<br /> 60179 fido FidoNet electronic mail and news network <br /> <br /> &lt;/source&gt;<br /> [[Category:Linux_Articles]]</div>

Qais http://www.initq.com/index.php/Installing_Bind 2011-10-06T16:35:11Z

<p>Qais: /* Where do I fit */</p> <hr /> <div>&lt;source lang=bash&gt;<br /> [root@localhost etc]# yum install bind.x86_64<br /> Loaded plugins: rhnplugin<br /> Setting up Install Process<br /> Resolving Dependencies<br /> --&gt; Running transaction check<br /> ---&gt; Package bind.x86_64 32:9.7.3-2.el6_1.P3.2 will be installed<br /> --&gt; Processing Dependency: bind-libs = 32:9.7.3-2.el6_1.P3.2 for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: liblwres.so.60()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: libisccfg.so.62()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: libisccc.so.60()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: libisc.so.62()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: libdns.so.69()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Processing Dependency: libbind9.so.60()(64bit) for package: 32:bind-9.7.3-2.el6_1.P3.2.x86_64<br /> --&gt; Running transaction check<br /> ---&gt; Package bind-libs.x86_64 32:9.7.3-2.el6_1.P3.2 will be installed<br /> --&gt; Finished Dependency Resolution<br /> <br /> Dependencies Resolved<br /> <br /> ======================================================================================<br /> Package Arch Version Repository Size<br /> ======================================================================================<br /> Installing:<br /> bind x86_64 32:9.7.3-2.el6_1.P3.2 rhel-x86_64-server-6 3.9 M<br /> Installing for dependencies:<br /> bind-libs x86_64 32:9.7.3-2.el6_1.P3.2 rhel-x86_64-server-6 838 k<br /> <br /> Transaction Summary<br /> ======================================================================================<br /> Install 2 Package(s)<br /> <br /> Total download size: 4.7 M<br /> Installed size: 0 <br /> Is this ok [y/N]: y<br /> Downloading Packages:<br /> (1/2): bind-9.7.3-2.el6_1.P3.2.x86_64.rpm | 3.9 MB 00:11 <br /> (2/2): bind-libs-9.7.3-2.el6_1.P3.2.x86_64.rpm | 838 kB 00:01 <br /> --------------------------------------------------------------------------------------<br /> Total 349 kB/s | 4.7 MB 00:13 <br /> Running rpm_check_debug<br /> Running Transaction Test<br /> Transaction Test Succeeded<br /> Running Transaction<br /> Installing : 32:bind-libs-9.7.3-2.el6_1.P3.2.x86_64 1/2 <br /> Installing : 32:bind-9.7.3-2.el6_1.P3.2.x86_64 2/2 <br /> <br /> Installed:<br /> bind.x86_64 32:9.7.3-2.el6_1.P3.2 <br /> <br /> Dependency Installed:<br /> bind-libs.x86_64 32:9.7.3-2.el6_1.P3.2 <br /> <br /> Complete!<br /> <br /> &lt;/source&gt;<br /> <br /> =Install Bind utilities=<br /> &lt;source lang=bash&gt;<br /> [root@localhost etc]# yum install bind-utils<br /> Loaded plugins: rhnplugin<br /> Setting up Install Process<br /> Resolving Dependencies<br /> --&gt; Running transaction check<br /> ---&gt; Package bind-utils.x86_64 32:9.7.3-2.el6_1.P3.2 will be installed<br /> --&gt; Finished Dependency Resolution<br /> <br /> Dependencies Resolved<br /> <br /> ======================================================================================<br /> Package Arch Version Repository Size<br /> ======================================================================================<br /> Installing:<br /> bind-utils x86_64 32:9.7.3-2.el6_1.P3.2 rhel-x86_64-server-6 177 k<br /> <br /> Transaction Summary<br /> ======================================================================================<br /> Install 1 Package(s)<br /> <br /> Total download size: 177 k<br /> Installed size: 0 <br /> Is this ok [y/N]: y<br /> Downloading Packages:<br /> bind-utils-9.7.3-2.el6_1.P3.2.x86_64.rpm | 177 kB 00:00 <br /> Running rpm_check_debug<br /> Running Transaction Test<br /> Transaction Test Succeeded<br /> Running Transaction<br /> Installing : 32:bind-utils-9.7.3-2.el6_1.P3.2.x86_64 1/1 <br /> <br /> Installed:<br /> bind-utils.x86_64 32:9.7.3-2.el6_1.P3.2 <br /> <br /> Complete!<br /> <br /> &lt;/source&gt;<br /> <br /> =Testing utilities=<br /> &lt;source lang=bash&gt;<br /> [root@localhost etc]# nslookup lexiana.com 207.69.188.185<br /> Server: 207.69.188.185<br /> Address: 207.69.188.185#53<br /> <br /> Non-authoritative answer:<br /> Name: lexiana.com<br /> Address: 99.54.115.122<br /> <br /> &lt;/source&gt;<br /> <br /> =Registration=<br /> Registration is a process by which a customer tells a registrar which nameservers to delegate a subdomain to and provides the registrar with contact and billing information. Some of these are Godaddy, VeriSign and Networksolutions.<br /> <br /> =Where do I fit=<br /> * http://www.allwhois.com<br /> <br /> Look for start of authority (SOA) record to get more information.<br /> <br /> &lt;source lang=bash&gt;<br /> [root@localhost etc]# nslookup - 207.69.188.185<br /> &gt; set type=soa<br /> &gt; lexiana.com<br /> Server: 207.69.188.185<br /> Address: 207.69.188.185#53<br /> <br /> Non-authoritative answer:<br /> lexiana.com<br /> origin = ns1.mydyndns.org<br /> mail addr = zone-admin.dyndns.com<br /> serial = 2007072046<br /> refresh = 10800<br /> retry = 1800<br /> expire = 604800<br /> minimum = 1800<br /> <br /> Authoritative answers can be found from:<br /> lexiana.com nameserver = ns3.mydyndns.org.<br /> lexiana.com nameserver = ns1.mydyndns.org.<br /> lexiana.com nameserver = ns4.mydyndns.org.<br /> lexiana.com nameserver = ns5.mydyndns.org.<br /> lexiana.com nameserver = ns2.mydyndns.org.<br /> ns1.mydyndns.org internet address = 204.13.248.76<br /> ns2.mydyndns.org internet address = 204.13.249.76<br /> ns2.mydyndns.org has AAAA address 2600:2002::76<br /> ns5.mydyndns.org internet address = 203.62.195.76<br /> ns5.mydyndns.org has AAAA address 2600:2005::76<br /> ns4.mydyndns.org internet address = 91.198.22.76<br /> ns4.mydyndns.org has AAAA address 2600:2004::76<br /> ns3.mydyndns.org internet address = 208.78.69.76<br /> &gt; <br /> [root@localhost etc]# nslookup <br /> &gt; set type=any<br /> &gt; lexiana.com.<br /> Server: 10.0.2.3<br /> Address: 10.0.2.3#53<br /> <br /> Non-authoritative answer:<br /> lexiana.com nameserver = ns1.mydyndns.org.<br /> lexiana.com nameserver = ns3.mydyndns.org.<br /> lexiana.com nameserver = ns5.mydyndns.org.<br /> lexiana.com nameserver = ns4.mydyndns.org.<br /> lexiana.com nameserver = ns2.mydyndns.org.<br /> <br /> Authoritative answers can be found from:<br /> &gt; set type=mx <br /> &gt; lexiana.com.<br /> Server: 10.0.2.3<br /> Address: 10.0.2.3#53<br /> <br /> Non-authoritative answer:<br /> lexiana.com mail exchanger = 5 mail.lexiana.com.<br /> <br /> Authoritative answers can be found from:<br /> &gt; <br /> <br /> <br /> &lt;/source&gt;<br /> [[Category:DNS]]</div>

Qais http://www.initq.com/index.php/Umask 2011-10-05T13:01:52Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:umask}} Octal value : Permission 0 : read, write and execute 1 : read and write 2 : read and execute 3 : read only 4 : write and execute ...&quot;</p> <hr /> <div>{{DISPLAYTITLE:umask}}<br /> Octal value : Permission<br /> 0 : read, write and execute<br /> 1 : read and write<br /> 2 : read and execute<br /> 3 : read only<br /> 4 : write and execute<br /> 5 : write only<br /> 6 : execute only<br /> 7 : no permissions<br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/WWN_numbers_on_linux 2011-10-03T17:46:55Z

<p>Qais: </p> <hr /> <div>cat /sys/class/scsi_host/hostn/device/fchost\:hostn/port_name<br /> <br /> where n is the host adapter number for your card.<br /> <br /> Then you can cat out the messages file and look for your card info to see which scsi host they got loaded on.<br /> <br /> &lt;source lang=bash&gt;<br /> [root@aoarnbnfu01 ~]# cat /sys/class/scsi_host/host<br /> host0/ host1/ host2/ host3/ host4/ host5/ <br /> <br /> [root@aoarnbnfu01 ~]# cat /sys/class/scsi_host/host0/device/fc_host\:host0/port_name <br /> 0x500110a00017a298<br /> [root@aoarnbnfu01 ~]# cat /sys/class/scsi_host/host1/device/fc_host\:host1/port_name <br /> 0x500110a00017a29a<br /> [root@aoarnbnfu01 ~]# cat /sys/class/scsi_host/host2/device/fc_host\:host2/port_name <br /> 0x10000000c9b3cf04<br /> [root@aoarnbnfu01 ~]# cat /sys/class/scsi_host/host3/device/fc_host\:host3/port_name <br /> 0x10000000c9b3cf05<br /> <br /> Sep 30 08:21:32 aoarnbnfu01 kernel: scsi0 : qla2xxx<br /> Sep 30 08:21:32 aoarnbnfu01 kernel: qla2xxx 0000:10:00.0: <br /> Sep 30 08:21:32 aoarnbnfu01 kernel: QLogic Fibre Channel HBA Driver: 8.03.01.05.05.06-k<br /> Sep 30 08:21:32 aoarnbnfu01 kernel: QLogic HPAE312A - PCI-Express Dual Port 4Gb Fibre Channel HBA<br /> <br /> Sep 30 08:21:33 aoarnbnfu01 kernel: Emulex LightPulse Fibre Channel SCSI driver 8.2.0.87.1p<br /> Sep 30 08:21:33 aoarnbnfu01 kernel: Copyright(c) 2004-2009 Emulex. All rights reserved.<br /> Sep 30 08:21:33 aoarnbnfu01 kernel: ACPI: PCI Interrupt 0000:13:00.0[A] -&gt; GSI 16 (level, low) -&gt; IRQ 50<br /> Sep 30 08:21:33 aoarnbnfu01 kernel: scsi2 : on PCI bus 13 device 00 irq 50<br /> &lt;/source&gt;<br /> <br /> =Method 2: /proc/scsi/{adapter-type}/{n} File=<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> bash-3.00# cat /proc/scsi/qla2xxx/1<br /> QLogic PCI to Fibre Channel Host Adapter for QLA2340-SUN:<br /> Firmware version 3.03.19 IPX, Driver version 8.01.04<br /> ISP: ISP2312, Serial# E71054<br /> Request Queue = 0x37dc0000, Response Queue = 0x37c50000<br /> Request Queue count = 2048, Response Queue count = 512<br /> Total number of active commands = 1<br /> Total number of interrupts = 5034411<br /> Device queue depth = 0x20<br /> Number of free request entries = 1264<br /> Number of mailbox timeouts = 0<br /> Number of ISP aborts = 0<br /> Number of loop resyncs = 0<br /> Number of retries for empty slots = 0<br /> Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0<br /> Host adapter:loop state = &lt;READY&gt;, flags = 0x1a03<br /> Dpc flags = 0x4000000<br /> MBX flags = 0x0<br /> Link down Timeout = 030<br /> Port down retry = 030<br /> Login retry count = 030<br /> Commands retried with dropped frame(s) = 0<br /> Product ID = 4953 5020 2020 0002<br /> <br /> <br /> SCSI Device Information:<br /> scsi-qla0-adapter-node=200000e08b870e30;<br /> scsi-qla0-adapter-port=210000e08b870e30;<br /> scsi-qla0-target-0=50060e8004295542;<br /> scsi-qla0-target-1=50060e8005bd3604;<br /> <br /> FC Port Information:<br /> scsi-qla0-port-0=50060e8004295509:50060e8004295509:3a000a:81;<br /> scsi-qla0-port-1=50060e8005bd3604:50060e8005bd3604:3a0036:82;<br /> <br /> SCSI LUN Information:<br /> (Id:Lun) * - indicates lun is not registered with the OS.<br /> ( 1: 0): Total reqs 2, Pending reqs 0, flags 0x0*, 0:0:82 00<br /> ( 1: 3): Total reqs 25133, Pending reqs 0, flags 0x0, 0:0:82 00<br /> ( 1: 4): Total reqs 5065249, Pending reqs 1, flags 0x0, 0:0:82 00<br /> <br /> &lt;/source&gt;<br /> [[Category:Linux_Articles]]</div>

Qais http://www.initq.com/index.php/Apt-get 2011-10-02T01:25:43Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:apt-get}} Category:Linux_Commands&quot;</p> <hr /> <div>{{DISPLAYTITLE:apt-get}}<br /> <br /> <br /> [[Category:Linux_Commands]]</div>

Qais http://www.initq.com/index.php/Managing_Users_on_Linux 2011-09-22T16:59:30Z

<p>Qais: Created page with &quot; adduser(8) - Command used to add user accounts. chage (1) - Used to change the time the user's password will expire. chfn(1) - Change a user's finger information ...&quot;</p> <hr /> <div><br /> adduser(8) - Command used to add user accounts.<br /> chage (1) - Used to change the time the user's password will expire.<br /> chfn(1) - Change a user's finger information<br /> chsh(1) - Change a user's shell.<br /> chgrp (1) - Changes the group ownership of files.<br /> chown (1) - Change the owner of file(s ) to another user.<br /> gpasswd (1) - Used to administer the /etc/group file.<br /> groupadd (8) - Create a new group.<br /> grpconv (8) - Creates /etc/gshadow from the file /etc/group which converts to shadow passwords.<br /> grpunconv (8)- Uses the files /etc/passwd and /etc/shadow to create /etc/passwd, then deletes /etc/shadow which converts from shadow passwords.<br /> groupdel (8) - Delete a group<br /> groupmod (8) - Modify a group<br /> groups (1) - print the groups a user is in<br /> grpck (8) - Verify the integrity of group files.<br /> id(1) - Print group or user ID numbers for the specified user.<br /> newgrp(1) - Allows a user to log in to a new group.<br /> newusers (8) - Update and create new users in batch form.<br /> nologin (5) - Prevent non-root users from logging onto the system.<br /> passwd (1) - Used to update a user's password. The command &quot;passwd username&quot; will set the password for the given user.<br /> pwconv (8) - Used to create the file /etc/shadow from the file /etc/passwd to convert to shadow passwords.<br /> pwunconv (8) - Uses the files /etc/passwd and /etc/shadow to create /etc/passwd, then deletes /etc/shadow to convert from shadow passwords.<br /> su (1) - run a shell with substitute user and group IDs<br /> useradd (8) - Create a new user or update default new user information<br /> userdel (8) - Delete a user account and their files from the system. The command &quot;userdel -r newuser&quot; will remove the user and deletes their home directory.<br /> usermod (8) - Modify a user account. <br /> <br /> [[Category:Linux_Commands]]</div>

Qais http://www.initq.com/index.php/Ln 2011-09-22T16:06:49Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:ln}}<br /> =Hard link=<br /> &lt;source lang=bash&gt;<br /> qais@debian60:~$ echo &quot;This is a file&quot; &gt; basic.file<br /> qais@debian60:~$ ln basic.file hardlink.file<br /> qais@debian60:~$ ls -lai *.file<br /> 644658 -rw-r--r-- 2 qais qais 15 Sep 21 13:23 basic.file<br /> 644658 -rw-r--r-- 2 qais qais 15 Sep 21 13:23 hardlink.file<br /> qais@debian60:~$ cat hardlink.file<br /> This is a file<br /> &lt;/source&gt;<br /> =Soft link=<br /> &lt;source lang=bash&gt;<br /> qais@debian60:~$ ln -s basic.file softlink.file<br /> qais@debian60:~$ ls -lai *.file<br /> 644658 -rw-r--r-- 2 qais qais 15 Sep 21 13:23 basic.file<br /> 644658 -rw-r--r-- 2 qais qais 15 Sep 21 13:23 hardlink.file<br /> 644821 lrwxrwxrwx 1 qais qais 10 Sep 21 13:24 softlink.file -&gt; basic.file<br /> qais@debian60:~$ cat softlink.file <br /> This is a file<br /> &lt;/source&gt;<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Pstree 2011-09-19T02:22:01Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:pstree}}<br /> pstree - display a tree of processes<br /> &lt;source lang=bash&gt;<br /> root@debian60:~/junk# pstree<br /> init─┬─NetworkManager─┬─dhclient<br /> │ └─{NetworkManager}<br /> ├─acpid<br /> ├─atd<br /> ├─avahi-daemon───avahi-daemon<br /> ├─bluetoothd<br /> ├─bonobo-activati───{bonobo-activat}<br /> ├─console-kit-dae───63*[{console-kit-da}]<br /> ├─cron<br /> ├─cupsd<br /> ├─2*[dbus-daemon]<br /> ├─exim4<br /> ├─gconfd-2<br /> ├─gdm3─┬─gdm-simple-slav─┬─Xorg<br /> │ │ ├─gdm-session-wor<br /> │ │ ├─gnome-session─┬─at-spi-registry<br /> │ │ │ ├─gdm-simple-gree<br /> │ │ │ ├─gnome-power-man<br /> │ │ │ ├─metacity<br /> │ │ │ ├─polkit-gnome-au<br /> │ │ │ └─{gnome-session}<br /> │ │ └─{gdm-simple-sla}<br /> │ └─{gdm3}<br /> ├─6*[getty]<br /> ├─gnome-settings-<br /> ├─gvfsd<br /> ├─kerneloops<br /> ├─modem-manager<br /> ├─polkitd<br /> ├─portmap<br /> ├─rpc.statd<br /> ├─rsyslogd───2*[{rsyslogd}]<br /> ├─sshd───sshd───sshd───bash───su───bash───pstree<br /> ├─udevd───2*[udevd]<br /> ├─upowerd<br /> └─wpa_supplicant<br /> &lt;/source&gt;<br /> <br /> =Flags=<br /> OPTIONS<br /> -a Show command line arguments. If the command line of a process is swapped out, that<br /> process is shown in parentheses. -a implicitly disables compaction for processes but<br /> not threads.<br /> <br /> -A Use ASCII characters to draw the tree.<br /> <br /> -c Disable compaction of identical subtrees. By default, subtrees are compacted whenever<br /> possible.<br /> <br /> -G Use VT100 line drawing characters.<br /> <br /> -h Highlight the current process and its ancestors. This is a no-op if the terminal<br /> doesn't support highlighting or if neither the current process nor any of its ances‐<br /> tors are in the subtree being shown.<br /> <br /> -H Like -h, but highlight the specified process instead. Unlike with -h, pstree fails<br /> when using -H if highlighting is not available.<br /> <br /> -l Display long lines. By default, lines are truncated to the display width or 132 if<br /> output is sent to a non-tty or if the display width is unknown.<br /> <br /> -n Sort processes with the same ancestor by PID instead of by name. (Numeric sort.)<br /> <br /> -p Show PIDs. PIDs are shown as decimal numbers in parentheses after each process name.<br /> -p implicitly disables compaction.<br /> <br /> -u Show uid transitions. Whenever the uid of a process differs from the uid of its par‐<br /> ent, the new uid is shown in parentheses after the process name.<br /> <br /> -U Use UTF-8 (Unicode) line drawing characters. Under Linux 1.1-54 and above, UTF-8 mode<br /> is entered on the console with echo -e '\033%8' and left with echo -e '\033%@'<br /> <br /> -V Display version information.<br /> <br /> -Z (SELinux) Show security context for each process. This flag will only work if pstree<br /> is compilied with SELinux support.<br /> <br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Cal 2011-09-19T01:07:52Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:cal}}<br /> <br /> cal, ncal — displays a calendar and the date of Easter<br /> <br /> &lt;source lang=bash&gt;<br /> root@debian60:~# cal<br /> September 2011<br /> Su Mo Tu We Th Fr Sa<br /> 1 2 3<br /> 4 5 6 7 8 9 10<br /> 11 12 13 14 15 16 17<br /> 18 19 20 21 22 23 24<br /> 25 26 27 28 29 30<br /> <br /> root@debian60:~# ncal<br /> September 2011<br /> Su 4 11 18 25<br /> Mo 5 12 19 26<br /> Tu 6 13 20 27<br /> We 7 14 21 28<br /> Th 1 8 15 22 29<br /> Fr 2 9 16 23 30<br /> Sa 3 10 17 24 <br /> <br /> root@debian60:~# cal -y 0001<br /> 1<br /> <br /> January February March<br /> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa<br /> 1 1 2 3 4 5 1 2 3 4 5<br /> 2 3 4 5 6 7 8 6 7 8 9 10 11 12 6 7 8 9 10 11 12<br /> 9 10 11 12 13 14 15 13 14 15 16 17 18 19 13 14 15 16 17 18 19<br /> 16 17 18 19 20 21 22 20 21 22 23 24 25 26 20 21 22 23 24 25 26<br /> 23 24 25 26 27 28 29 27 28 27 28 29 30 31<br /> 30 31 <br /> April May June<br /> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa<br /> 1 2 1 2 3 4 5 6 7 1 2 3 4<br /> 3 4 5 6 7 8 9 8 9 10 11 12 13 14 5 6 7 8 9 10 11<br /> 10 11 12 13 14 15 16 15 16 17 18 19 20 21 12 13 14 15 16 17 18<br /> 17 18 19 20 21 22 23 22 23 24 25 26 27 28 19 20 21 22 23 24 25<br /> 24 25 26 27 28 29 30 29 30 31 26 27 28 29 30<br /> <br /> July August September<br /> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa<br /> 1 2 1 2 3 4 5 6 1 2 3<br /> 3 4 5 6 7 8 9 7 8 9 10 11 12 13 4 5 6 7 8 9 10<br /> 10 11 12 13 14 15 16 14 15 16 17 18 19 20 11 12 13 14 15 16 17<br /> 17 18 19 20 21 22 23 21 22 23 24 25 26 27 18 19 20 21 22 23 24<br /> 24 25 26 27 28 29 30 28 29 30 31 25 26 27 28 29 30<br /> 31 <br /> October November December<br /> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa<br /> 1 1 2 3 4 5 1 2 3<br /> 2 3 4 5 6 7 8 6 7 8 9 10 11 12 4 5 6 7 8 9 10<br /> 9 10 11 12 13 14 15 13 14 15 16 17 18 19 11 12 13 14 15 16 17<br /> 16 17 18 19 20 21 22 20 21 22 23 24 25 26 18 19 20 21 22 23 24<br /> 23 24 25 26 27 28 29 27 28 29 30 25 26 27 28 29 30 31<br /> 30 31 <br /> <br /> root@debian60:~# cal -m 12<br /> December 2011<br /> Su Mo Tu We Th Fr Sa<br /> 1 2 3<br /> 4 5 6 7 8 9 10<br /> 11 12 13 14 15 16 17<br /> 18 19 20 21 22 23 24<br /> 25 26 27 28 29 30 31<br /> <br /> root@debian60:~# cal | sed 's/2011/2000/' <br /> September 2000<br /> Su Mo Tu We Th Fr Sa<br /> 1 2 3<br /> 4 5 6 7 8 9 10<br /> 11 12 13 14 15 16 17<br /> 18 19 20 21 22 23 24<br /> 25 26 27 28 29 30<br /> <br /> &lt;/source&gt;<br /> [[Category:Linux_Commands]]</div>

Qais http://www.initq.com/index.php/Chage 2011-09-18T19:18:45Z

<p>Qais: /* How to disable password aging for an user account */</p> <hr /> <div>{{DISPLAYTITLE:chage}}<br /> <br /> chage stands for “change age”. i.e chage command abbreviation<br /> <br /> &lt;source lang=bash&gt;<br /> [root@localhost profile.d]# chage --list a507394<br /> Last password change : Apr 10, 2011<br /> Password expires : never<br /> Password inactive : never<br /> Account expires : never<br /> Minimum number of days between password change : 0<br /> Maximum number of days between password change : 99999<br /> Number of days of warning before password expires : 7<br /> &lt;/source&gt;<br /> <br /> =Password Expiry Date for an user using chage option -M=<br /> Please note that option -M will update both “Password expires” and “Maximum number of days between password change” entries as shown below.<br /> <br /> &lt;source lang=bash&gt;<br /> # chage -M 10 dhinesh<br /> <br /> # chage --list dhinesh<br /> Last password change : Apr 23, 2009<br /> Password expires : May 03, 2009<br /> Password inactive : never<br /> Account expires : never<br /> Minimum number of days between password change : 0<br /> Maximum number of days between password change : 10<br /> Number of days of warning before password expires : 7<br /> &lt;/source&gt;<br /> <br /> =Account Expiry Date for an User=<br /> You can also use chage command to set the account expiry date as shown below using option -E. The date given below is in “YYYY-MM-DD” format. This will update the “Account expires” value as shown below.<br /> &lt;source lang=bash&gt;<br /> # chage -E &quot;2009-05-31&quot; dhinesh<br /> <br /> # chage -l dhinesh<br /> Last password change : Apr 23, 2009<br /> Password expires : May 03, 2009<br /> Password inactive : never<br /> Account expires : May 31, 2009<br /> Minimum number of days between password change : 0<br /> Maximum number of days between password change : 10<br /> Number of days of warning before password expires : 7<br /> &lt;/source&gt;<br /> <br /> =Force the user account to be locked after X number of inactivity days=<br /> <br /> Typically if the password is expired, users are forced to change it during their next login. You can also set an additional condition, where after the password is expired, if the user never tried to login for 10 days, you can automatically lock their account using option -I as shown below. In this example, the “Password inactive” date is set to 10 days from the “Password expires” value.<br /> <br /> Once an account is locked, only system administrators will be able to unlock it.<br /> &lt;source lang=bash&gt;<br /> # chage -I 10 dhinesh<br /> <br /> # chage -l dhinesh<br /> Last password change : Apr 23, 2009<br /> Password expires : May 03, 2009<br /> Password inactive : May 13, 2009<br /> Account expires : May 31, 2009<br /> Minimum number of days between password change : 0<br /> Maximum number of days between password change : 10<br /> Number of days of warning before password expires : 7<br /> &lt;/source&gt;<br /> <br /> =How to disable password aging for an user account=<br /> To turn off the password expiration for an user account, set the following:<br /> <br /> * -m 0 will set the minimum number of days between password change to 0<br /> * -M 99999 will set the maximum number of days between password change to 99999<br /> * -I -1 (number minus one) will set the “Password inactive” to never<br /> * -E -1 (number minus one) will set “Account expires” to never.<br /> <br /> &lt;source lang=bash&gt;<br /> # chage -m 0 -M 99999 -I -1 -E -1 dhinesh<br /> <br /> # chage --list dhinesh<br /> Last password change : Apr 23, 2009<br /> Password expires : never<br /> Password inactive : never<br /> Account expires : never<br /> Minimum number of days between password change : 0<br /> Maximum number of days between password change : 99999<br /> Number of days of warning before password expires : 7<br /> &lt;/source&gt;<br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Realtek_debian_squeeze_issue 2011-09-18T00:11:06Z

<p>Qais: Created page with &quot;Installing the new kernel package &quot;linux-image-2.6.32-trunk-amd64&quot; results in new warning messages like: W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r...&quot;</p> <hr /> <div>Installing the new kernel package &quot;linux-image-2.6.32-trunk-amd64&quot;<br /> results in new warning messages like:<br /> <br /> W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169<br /> <br /> It looks like this firmware was removed from the kernel proper as part<br /> of the non-free firmware removal process, which suggests that it should<br /> be included in firmware-linux-nonfree instead.<br /> <br /> downloaded the firmware from<br /> * http://packages.debian.org/squeeze/all/firmware-realtek/download<br /> <br /> firmware gets installed at<br /> <br /> root@lexiana:/lib/firmware/rtl_nic# pwd<br /> <br /> /lib/firmware/rtl_nic<br /> <br /> root@lexiana:/lib/firmware/rtl_nic# ls<br /> <br /> rtl8168d-1.fw rtl8168d-2.fw<br /> <br /> ran update-initramfs -u. <br /> <br /> following a reboot kern.log had changed:<br /> <br /> WAS:<br /> <br /> Jan 17 23:26:00 gauss kernel: [ 1.001780] r8169 0000:02:00.0:firmware: requesting rtl8168d-2.fw<br /> Jan 17 23:26:00 gauss kernel: [ 1.002981] eth0: unable to apply firmware patch<br /> <br /> IS:<br /> <br /> Jan 22 09:52:54 gauss kernel: [ 0.998226] r8169 0000:02:00.0:firmware: requesting rtl_nic/rtl8168d-2.fw<br /> [[Category:Linux_Articles]]</div>

Qais http://www.initq.com/index.php/Chkconfig 2011-09-16T17:14:42Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:chkconfig}}<br /> <br /> =List the start scripts=<br /> * chkconfig --list<br /> * chkconfig --list | grep proxy-forward<br /> <br /> =Enable a start script=<br /> * chkconfig --level 345 proxy-forward on<br /> <br /> =Writing a start script=<br /> &lt;source lang=bash&gt;<br /> #!/bin/sh<br /> #<br /> # Apache proxy forward script<br /> #<br /> # Version 1.0 - Qais Chaudry 20110816<br /> # qais.chaudry@atos.net<br /> #<br /> # chkconfig: 345 99 50<br /> # description: proxy-forward is used for forwarding all port 80 \<br /> # traffic to a loadbalancer at port 8080.<br /> #<br /> <br /> case &quot;$1&quot; in<br /> start)<br /> /opt/httpd-2.2.19/bin/apachectl start<br /> ;;<br /> <br /> stop)<br /> <br /> kill -9 `ps -ef|grep https|grep -v grep|awk '{print $2}'`<br /> <br /> ;;<br /> <br /> *)<br /> echo $&quot;Usage: $0 {start|stop}&quot;<br /> exit 2<br /> <br /> esac<br /> <br /> exit 0<br /> &lt;/source&gt;<br /> <br /> =Enable your own start script=<br /> $ /sbin/chkconfig llc2 on<br /> <br /> service llc2 does not support chkconfig<br /> <br /> it look like chkconfig looks for a line similar to the following in each run control script:<br /> <br /> # chkconfig: 345 99 50<br /> <br /> The values after the “chkconfig:” statement contain the runlevels to enable the script at, the value to use after the “S” in the start scripts, and the value to use after the “K” in the kill scripts. So 345 would cause the start script to be executed at run levels 3, 4 and 5, the start script would be named S99llc2, and the kill script would be named K50llc2.<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Diff 2011-09-11T02:24:13Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:diff}} use diff for ascii file and use '''cmp''' for binary files. Category:Bash Category:Linux Commands&quot;</p> <hr /> <div>{{DISPLAYTITLE:diff}}<br /> <br /> use diff for ascii file and use '''cmp''' for binary files.<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Wall 2011-09-11T02:13:37Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:wall}}<br /> &lt;source lang=bash&gt;<br /> root@initq:~# wall mount.sh<br /> &lt;/source&gt;<br /> <br /> You can also type '''wall''' then your message and then CTRL-D to send the message.<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Write 2011-09-11T02:05:21Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:write}}<br /> &lt;source lang=bash&gt;<br /> w<br /> 21:04:42 up 5 days, 9:09, 3 users, load average: 0.26, 0.16, 0.15<br /> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT<br /> lexiana tty8 :0 Thu17 5days 2:46m 0.57s gnome-session --session=ubuntu<br /> lexiana pts/0 :0 Thu17 0.00s 1.32s 42.37s gnome-terminal<br /> lexiana pts/1 :0 Thu19 40.00s 0.74s 0.74s bash<br /> root@initq:~# write lexiana tty8<br /> write: write: you have write permission turned off.<br /> <br /> write: warning: write will appear from lexiana<br /> hello<br /> ^Croot@initq:~#<br /> &lt;/source&gt;<br /> <br /> If you don't like to see message then do<br /> * mesg n<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Who 2011-09-11T01:38:08Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:who}}<br /> &lt;source lang=bash&gt;<br /> # who am i<br /> lexiana pts/0 2011-09-08 17:26 (:0)<br /> <br /> # whoami<br /> root<br /> <br /> # who<br /> lexiana tty8 2011-09-08 17:26 (:0)<br /> lexiana pts/0 2011-09-08 17:26 (:0)<br /> lexiana pts/1 2011-09-08 19:03 (:0)<br /> <br /> # w<br /> 20:51:19 up 5 days, 8:56, 3 users, load average: 0.26, 0.21, 0.17<br /> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT<br /> lexiana tty8 :0 Thu17 5days 2:45m 0.57s gnome-session -<br /> lexiana pts/0 :0 Thu17 0.00s 1.25s 40.38s gnome-terminal<br /> lexiana pts/1 :0 Thu19 3:49m 0.71s 0.71s bash<br /> <br /> # finger<br /> Login Name Tty Idle Login Time Office Office Phone<br /> lexiana lexiana tty8 5d Sep 8 17:26 (:0)<br /> lexiana lexiana *pts/0 Sep 8 17:26 (:0)<br /> lexiana lexiana pts/1 3:49 Sep 8 19:03 (:0)<br /> &lt;/source&gt;<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Locate 2011-09-11T01:36:47Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:locate}} Category:Bash Category:Linux Commands&quot;</p> <hr /> <div>{{DISPLAYTITLE:locate}}<br /> <br /> <br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Apropos 2011-09-11T00:51:00Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:apropos}}<br /> <br /> man -k gives the same output.<br /> <br /> whatis<br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Which 2011-09-11T00:46:35Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:which}} =which= =whereis= Category:Bash Category:Linux Commands&quot;</p> <hr /> <div>{{DISPLAYTITLE:which}}<br /> =which=<br /> <br /> =whereis=<br /> <br /> <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/If_than_examples 2011-09-10T21:37:43Z

<p>Qais: </p> <hr /> <div>&lt;source lang=bash&gt;<br /> #!/bin/sh<br /> set +<br /> echo &quot;Is it morning? Please answer yes or no&quot;<br /> read timeofday<br /> <br /> if [ $timeofday = yes ]<br /> then<br /> echo &quot;Good morning&quot;<br /> elif [ $timeofday = no ]<br /> then<br /> echo &quot;Good evening&quot;<br /> else<br /> echo &quot;Input in invalid&quot;<br /> exit 1;<br /> fi<br /> <br /> exit 0<br /> &lt;/source&gt;<br /> <br /> &lt;source lang=bash&gt;<br /> $ ./morning.sh <br /> Is it morning? Please answer yes or no<br /> yes<br /> Good morning<br /> $ ./morning.sh <br /> Is it morning? Please answer yes or no<br /> no<br /> Good evening<br /> $ ./morning.sh <br /> Is it morning? Please answer yes or no<br /> oh no<br /> [: 15: oh: unexpected operator<br /> [: 15: oh: unexpected operator<br /> Input in invalid<br /> <br /> &lt;/source&gt;<br /> <br /> If you do not enter yes or no and just hit enter then you will get<br /> &lt;source lang=bash&gt;<br /> $ ./morning.sh <br /> Is it morning? Please answer yes or no<br /> <br /> [: 15: =: unexpected operator<br /> [: 15: =: unexpected operator<br /> Input in invalid<br /> &lt;/source&gt;<br /> <br /> To avoid this you have to put $timeofday in quotes. &quot;$timeofday&quot;<br /> [[Category:Bash_Projects]]</div>

Qais http://www.initq.com/index.php/Test 2011-09-10T20:50:57Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:test}} test Evaluate a conditional expression expr. Syntax test expr [ expr Options Each operator and operand must be a separate argument. When t...&quot;</p> <hr /> <div>{{DISPLAYTITLE:test}}<br /> test<br /> Evaluate a conditional expression expr.<br /> <br /> Syntax<br /> test expr<br /> [ expr<br /> <br /> Options<br /> <br /> Each operator and operand must be a separate argument. When the [ form is used, the last argument to the command must be a ]. Expressions may be combined using the following operators, listed in decreasing order of precedence.<br /> <br /> ! expr<br /> <br /> True if expr is false.<br /> <br /> ( expr )<br /> <br /> Returns the value of expr. This may be used to override the<br /> normal precedence of operators. <br /> <br /> expr1 -a expr2<br /> <br /> True if both expr1 and expr2 are true.<br /> <br /> expr1 -o expr2<br /> <br /> True if either expr1 or expr2 is true.<br /> <br /> The test and [ builtins evaluate conditional expressions using a set of rules based on the number of arguments.<br /> <br /> 0 arguments<br /> <br /> The expression is false.<br /> 1 argument<br /> <br /> The expression is true if and only if the argument is not null.<br /> 2 arguments<br /> <br /> If the first argument is `!', the expression is true if and only if the second argument is null. If the first argument is one of the unary conditional operators, the expression is true if the unary test is true. If the first argument is not a valid unary operator, the expression is false.<br /> 3 arguments<br /> <br /> If the second argument is one of the binary conditional operators, the result of the expression is the result of the binary test using the first and third arguments as operands. If the first argument is `!', the value is the negation of the two-argument test using the second and third arguments. If the first argument is exactly `(' and the third argument is exactly `)', the result is the one-argument test of the second argument. Otherwise, the expression is false. The `-a' and `-o' operators are considered binary operators in this case.<br /> 4 arguments<br /> <br /> If the first argument is `!', the result is the negation of the three-argument expression composed of the remaining arguments. Otherwise, the expression is parsed and evaluated according to precedence using the rules listed above.<br /> 5 or more arguments<br /> <br /> The expression is parsed and evaluated according to precedence using the rules listed above.<br /> <br /> The above applies to the BOURNE shell built-in, the BASH `test' command has the following additional options:<br /> <br /> File type tests<br /> <br /> These options test for particular types of files. All cases will only return True (0) if the file exists.<br /> <br /> `-b file'<br /> True if file is a Block special device.<br /> <br /> `-c file'<br /> True if file is a Character special device.<br /> <br /> `-d file'<br /> True if file is a Directory.<br /> <br /> `-e file'<br /> True if file Exists.<br /> <br /> `-f file'<br /> True if file is a regular File.<br /> <br /> `-g file'<br /> True if file has its set-group-id bit set.<br /> <br /> `-G file'<br /> True if file is owned by the current effective group id.<br /> <br /> `-k file'<br /> True if file has its &quot;sticky&quot; bit set.<br /> <br /> `-h file'<br /> `-L file'<br /> True if file is a symbolic Link.<br /> <br /> `-O file'<br /> True if file is owned by the current effective user id.<br /> <br /> `-p file'<br /> True if file is a named Pipe.<br /> <br /> `-r file'<br /> True if file is readable.<br /> <br /> `-S file'<br /> True if file is a Socket.<br /> <br /> `-s file'<br /> True if file has a Size greater than zero.<br /> <br /> `-t [FD]'<br /> True if FD is opened on a terminal. If FD is omitted, it defaults<br /> to 1 (standard output).<br /> <br /> `-u file'<br /> True if file has its set-user-id bit set.<br /> <br /> `-w file'<br /> True if file is writable.<br /> <br /> `-x file'<br /> True if file is executable.<br /> <br /> `file1 -ef file2'<br /> True if file1 and file2 have the same device and inode numbers,<br /> i.e., if they are hard links to each other.<br /> <br /> File Age<br /> These options test the file modification date.<br /> <br /> `file1 -nt file2'<br /> True if file1 is newer than file2.<br /> <br /> `file1 -ot file2'<br /> True if file1 is older than file2.<br /> <br /> String tests<br /> These options test string characteristics. Strings are not quoted for `test', though you may need to quote them to protect characters with special meaning to the shell, e.g., spaces.<br /> <br /> `-z String'<br /> True if the length of String is zero.<br /> <br /> `-n String'<br /> `String'<br /> True if the length of String is nonzero.<br /> <br /> `String1 = String2'<br /> True if the strings are equal.<br /> <br /> `String1 != String2'<br /> True if the strings are not equal.<br /> <br /> Numeric tests<br /> Numeric relationals. The arguments must be entirely numeric (possibly negative), or the special expression `-l STRING', which evaluates to the length of STRING.<br /> <br /> `ARG1 -eq ARG2'<br /> `ARG1 -ne ARG2'<br /> `ARG1 -lt ARG2'<br /> `ARG1 -le ARG2'<br /> `ARG1 -gt ARG2'<br /> `ARG1 -ge ARG2'<br /> These arithmetic binary operators return true if ARG1 is equal,<br /> not-equal, less-than, less-than-or-equal, greater-than, or<br /> greater-than-or-equal than ARG2, respectively.<br /> <br /> For example:<br /> <br /> test -1 -gt -2 &amp;&amp; echo yes<br /> =&gt; yes<br /> test -l abc -gt 1 &amp;&amp; echo yes<br /> =&gt; yes<br /> test 0x100 -eq 1<br /> error--&gt; test: integer expression expected before -eq<br /> <br /> Examples<br /> <br /> $ ls -al<br /> total 67<br /> <br /> drwxr-xr-x 18 root root 4096 Jun 9 21:12 ./<br /> drwxr-xr-x 18 root root 4096 Jun 9 21:12 ../<br /> -rw-rw-rw- 1 simon users 4096 Jun 9 07:30 london<br /> -rwsrwsrwx 1 simon users 4096 Jun 9 07:32 aberdeen<br /> -rw------- 1 simon users 4096 Jun 9 07:29 bristol<br /> -rw-r--r-- 1 simon users 4096 Jun 9 07:29 bath<br /> $<br /> <br /> $ test -r paris<br /> $ echo $?<br /> 1<br /> $<br /> <br /> Because the file `paris' is not Readable, the value returned is false (non zero)<br /> <br /> if [ &quot;$LOGNAME&quot; = &quot;scott&quot; ]<br /> then<br /> echo &quot;Logged in as Scott&quot;<br /> else<br /> echo &quot;incorrect user&quot;<br /> fi<br /> <br /> If the logname variable = scott then the test returns TRUE (0)<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/Environment_variables_script 2011-09-10T20:03:26Z

<p>Qais: </p> <hr /> <div>In this script we will also use [ or test to check if a file exists.<br /> <br /> &lt;source lang=bash&gt;<br /> #!/bin/sh<br /> if [ -f try_var.sh ]<br /> then<br /> salutation=&quot;Hello&quot;<br /> echo $salutation<br /> echo &quot;The program $0 is now running&quot;<br /> echo &quot;The second parameter is $2&quot;<br /> echo &quot;The first parameter is $1&quot;<br /> echo &quot;The parameter list was $*&quot;<br /> echo &quot;The users home directory is $HOME&quot;<br /> <br /> echo &quot;Please enter a new greeting&quot;<br /> read salutation<br /> <br /> echo $salutation<br /> echo &quot;The script is now complete&quot;<br /> fi<br /> exit 0<br /> <br /> <br /> $ ./try_var.sh bus khlas<br /> Hello<br /> The program ./try_var.sh is now running<br /> The second parameter is khlas<br /> The first parameter is bus<br /> The parameter list was bus khlas<br /> The users home directory is /home/lexiana<br /> Please enter a new greeting<br /> olaf<br /> olaf<br /> The script is now complete<br /> <br /> &lt;/source&gt;<br /> <br /> [[Category:Bash_Projects]]</div>

Qais http://www.initq.com/index.php/Setting_up_NFS 2011-09-07T09:17:20Z

<p>Qais: </p> <hr /> <div>=Server=<br /> * # apt-get install nfs-kernel-server <br /> =Export=<br /> File to edit is /etc/exports<br /> <br /> * /export 192.168.1.0/24(rw,fsid=0,insecure,no_subtree_check,async)<br /> =Client=<br /> * # apt-get install nfs-common <br /> [[Category:Linux Articles]]</div>

Qais http://www.initq.com/index.php/Language 2011-09-05T03:39:46Z

<p>Qais: Created page with &quot;=Ding= * http://www-user.tu-chemnitz.de/~fri/ding/ German &lt;--&gt; English program. Can be used for a spell checker. Category:Utilities&quot;</p> <hr /> <div>=Ding=<br /> * http://www-user.tu-chemnitz.de/~fri/ding/<br /> German &lt;--&gt; English program. Can be used for a spell checker. <br /> <br /> [[Category:Utilities]]</div>

Qais http://www.initq.com/index.php/Chmod 2011-09-05T00:41:23Z

<p>Qais: </p> <hr /> <div>{{DISPLAYTITLE:chmod}}<br /> =Change to 777=<br /> * chmod u=+rwx,g=+rwx,o=+rwx setuid.txt<br /> <br /> =Change to 000=<br /> * chmod u=-rwx,g=-rwx,o=-rwx setuid.txt<br /> <br /> =Sticky Bit=<br /> As of SUID or SetUID bit, the executable which has the SUID set runs with the ownership of the program owner. That is, if you own an executable, and another person issues the executable, then it runs with your permission and not his. The default is that a program runs with the ownership of the person executing the binary.<br /> <br /> * chmod g+s /home/software<br /> <br /> =Permissions=<br /> * r is 4<br /> * w is 2<br /> * x is 1<br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]</div>

Qais http://www.initq.com/index.php/For_and_if_example 2011-09-05T00:23:16Z

<p>Qais: </p> <hr /> <div>* bash# for file in *; do if grep -q EMAIL $file; then echo $file; fi;done;<br /> &lt;source lang=bash&gt;<br /> #!/bin/sh<br /> <br /> #This script gives the name of the matching word in all files.<br /> <br /> for file in *<br /> do<br /> if grep -q EMAIL $file<br /> then<br /> echo $file<br /> fi<br /> done<br /> <br /> exit 0<br /> &lt;/source&gt;<br /> <br /> The output will be just file names because grep -q means quiet.<br /> <br /> =Check if Number is even or odd=<br /> <br /> Write a script that prints all odd or even numbers. mod % (returns the remainder of an integer division operation).<br /> <br /> &lt;source lang=bash&gt;<br /> #!/bin/bash<br /> <br /> for n in {1..100}<br /> do<br /> out=$(( $n % 2 ))<br /> if [ $out -eq 0 ]<br /> then<br /> echo &quot;$n is even number&quot;<br /> else<br /> echo &quot;$n is odd number&quot;<br /> fi<br /> done;<br /> <br /> &lt;/source&gt;<br /> <br /> =For example for fsck=<br /> &lt;source lang=bash&gt;<br /> for i in `cat /etc/fstab | grep -i sda1 | awk '{print $1}'`; do fsck $i; done<br /> &lt;/source&gt;<br /> [[Category:Bash_Projects]]</div>

Qais http://www.initq.com/index.php/Pgrep 2011-09-04T23:28:10Z

<p>Qais: Created page with &quot;{{DISPLAYTITLE:pgrepl}} pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to stdout. All the criteria have to mat...&quot;</p> <hr /> <div>{{DISPLAYTITLE:pgrepl}}<br /> pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to stdout. All the criteria have to match. For example,<br /> <br /> pgrep -u root sshd<br /> <br /> will only list the processes called sshd AND owned by root. On the other hand,<br /> <br /> pgrep -u root,daemon<br /> <br /> will list the processes owned by root OR daemon. <br /> [[Category:Bash]]<br /> [[Category:Linux Commands]]<br /> [[Category:LPI]]</div>

Qais