[ilugd] [COMMERCIAL] Immediate requirement of System Administrator at HCL
Designation: Linux Specialist. Location: Noida, India. Job Description / Responsibility Should have around 5+ year of UNIX experience with 4+ years of demonstrated experience and proficiency in managing and maintaining Linux environment, will be responsible for - Installation/Upgrade Configuration of Servers - Network Configuration, Firmware Install, OS Install, Filesystem Configuration. - User Admin on UNIX servers * Jumpstart Environment Management - Develop Standards Policies, Set Images, develop/Maintain scripts. - Patch implementation maintenance * Licensing * Boot Prom Management * Performance Management. - Service Management - NIS/NIS+/DNS/NFS/Samba/Send Mail * Capacity Planning. - Security Administration - Add/remove/Troubleshoot Security Policies. - Tools Administration - Agent Installation * Device Management - Installing Configuring devices. - Syslog Log management * Documentation - Systems/tool/Service management documents update. - Process related activities * Scripts Maintenance. - This role also needs the person to perform Webmaster / Admin Activities on Apache / Tomcat or any other Webservers. - Knowledge of Remedy ticketing will be a plus. Qualifications: Bachelors degree in Engineering (in Computer Science/ Electrical/ Electronic/ Communication) or Any Degree. Key Skills: 1 Good Business Understanding 2 Problem solving and analysis 3 Global orientation 4 Good communication skills 5 Process oriented 6 Attention to detail 7 Ability to stay focused Contact Information: Atul Kumar [EMAIL PROTECTED] Regards, Atul DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
From the man pages of uptime, you get Print the current time, the length of time the system has been up, the number of users on the system, and the average number of jobs in the run queue over the last 1, 5 and 15 minutes. The above does not seem to match on my system (Ubuntu Feisty). $ man uptime ``` uptime gives a one line display of the following information. The current time, how long the system has been running, how many users are currently logged on, and the system load averages for the past 1, 5,and 15 minutes. ``` It gives no mention of run queue. But when actually you run uptime, you get load average instead [EMAIL PROTECTED]:/var/log/sa uptime 12:36pm up 223 days 3:05, 1 user, load average: 0.00, 0.00, 0.00 How does the jobs in the queue and load average relates to each other. could anybody help me to understand ? Read here for detailed explanation of Load Averages. http://www.teamquest.com/resources/gunther/display/5/index.htm -- o1p2e3n4g5l6 http://saleem.a.ansari.googlepages.com/ http://www.jmilug.org/ http://www.csijmi.com/ Linux User #414799 (http://counter.li.org/) ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ,--[ On Wed, Nov 21, 2007 at 12:42:13PM +, Yashpal Nagar wrote: | Hi All, | | From the man pages of uptime, you get | | Print the current time, the length of time the system has been up, | the number of users on the system, and the average number of jobs | in the run queue over the last 1, 5 and 15 minutes. | | But when actually you run uptime, you get load average instead | [EMAIL PROTECTED]:/var/log/sa uptime | 12:36pm up 223 days 3:05, 1 user, load average: 0.00, 0.00, 0.00 | | How does the jobs in the queue and load average relates to each other. could | anybody help me to understand ? http://en.wikipedia.org/wiki/Load_(computing) | | Regards | Yash HTH - -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHRFbPHy+EEHYuXnQRArvpAJ9eLcFogXQAxtVHMKh9rXk/lxrgNgCggGNG brJ2Ewso/AwBnDDJXSLvK0w= =UMLp -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
On Wednesday 21 Nov 2007, Yashpal Nagar wrote: Hi All, From the man pages of uptime, you get Print the current time, the length of time the system has been up, the number of users on the system, and the average number of jobs in the run queue over the last 1, 5 and 15 minutes. But when actually you run uptime, you get load average instead [EMAIL PROTECTED]:/var/log/sa uptime 12:36pm up 223 days 3:05, 1 user, load average: 0.00, 0.00, 0.00 How does the jobs in the queue and load average relates to each other. could anybody help me to understand ? This has been explained a number of times. The last time was in 2004 :) http://thread.gmane.org/gmane.user-groups.linux.delhi/7466/focus=7487 There was also a post on LIH in (yes!) 2001 by yours truly. Enclosing that: In Unix, a user process can be either ready to run or waiting for some event (eg I/O completion, sleep, etc). The system splits processor time between ready-to-run processes through the scheduling algorithm built into the kernel. At any given time, then, one process is running while other ready-to-run processes are waiting for their turn on the processor(s). (This is ignoring the kernel itself, which also uses the processor.) The three load average numbers are the average number of processes which were ready to run and awaiting their turn on the processor in the past 1, 5 and 15 minutes. In other words, a first load average number of 7 would mean that in the past minute, at any given time, on the average there were 7 processes which were ready to run but not running due to lack of processor time. So in a sense the load average is a measure of the load on the system. Higher load averages mean that the processor is unable to handle the demands put onto it by the tasks running in the system. However, there are no fixed measures for defining what load average is high and what is low. I personally would start getting worried if a server under my control was consistently showing load averages higher than, say, 5; on the other hand, it all depends on what sort of tasks the server is doing and how fast and often the kernel does context switches. Regards, -- Raju -- Raj Mathur[EMAIL PROTECTED] http://kandalaya.org/ Freedom in Technology Software || February 2008 || http://freed.in/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F PsyTrance Chill: http://schizoid.in/ || It is the mind that moves ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
[ilugd] [OT] Converting a non network printer to a network printer
Hi, I have 2 computers at home, one desktop computer and a laptop. I share my internet connection using a wireless router, hence have both my computers are also on a network.I have printer(HP 5600 officejet all in 1) at home which doesnt have an ethernet port for me connect it to a network. I was thinking if its possible for me to connect my printer to the router by using a USB to LAN converter. So essentially what I mean is Printer's USB cord - USBtoLAN Converter(this gives me an ethernet port) - router (using a cable) Will this allow me to print from desktop and laptop?? or maybe my question should be will my printer be able to accquire an ip address from the dhcp on the router, and will this be accessible to me over the network for printing?? Any other suggestions for converting the non network printer to a networked one?? thanks -- Puneet http://sahyog.blogspot.com/ ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
Saleem Ansari wrote: Read here for detailed explanation of Load Averages. http://www.teamquest.com/resources/gunther/display/5/index.htm Very interesting to know the difference between cpu utilization and load. Do you also know where are the Dr. Gunther's Quiz answers? http://www.teamquest.com/resources/gunther/display/4/index.htm Regards Yash ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
Raj Mathur wrote: So in a sense the load average is a measure of the load on the system. Higher load averages mean that the processor is unable to handle the demands put onto it by the tasks running in the system. However, there are no fixed measures for defining what load average is high and what is low. I personally would start getting worried if a server under my control was consistently showing load averages higher than say, 5; on the other hand, it all depends on what sort of tasks the server is doing and how fast and often the kernel does context switches. Apart from uptime, which tells about the load average in the form of average number of processes essentially in run_queue at a time, over last 1 minute, 5 minute and 15 minutes. There is another program called System Acitivty Report (SAR) which represents the CPU utilization in the form of percentages. The CPU load monitored by SAR is shown in % [EMAIL PROTECTED]:/var/log/sa sar -f sa31|more Linux 2.6.16.21-0.8-default (hostux2) 31/08/07 00:00:26CPU %user %nice %system %iowait %steal %idle 00:01:26all 0.98 0.00 0.53 0.78 0.00 97.70 00:02:26all 0.80 0.00 0.33 0.65 0.00 98.22 How does this % relates to the uptime output? Does this % refers to the run_queue capacity? Is there any way we can modify run_queue. In SAR's case, is it fair to sum the % of queues (excluding %idle) and conclude that as the total CPU load at that time? Regards Yash ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 22 Nov 2007, Yashpal Nagar wrote: Raj Mathur wrote: So in a sense the load average is a measure of the load on the system. Higher load averages mean that the processor is unable to handle the demands put onto it by the tasks running in the system. However, there are no fixed measures for defining what load average is high and what is low. I personally would start getting worried if a server under my control was consistently showing load averages higher than say, 5; on the other hand, it all depends on what sort of tasks the server is doing and how fast and often the kernel does context switches. Apart from uptime, which tells about the load average in the form of average number of processes essentially in run_queue at a time, over last 1 minute, 5 minute and 15 minutes. There is another program called System Acitivty Report (SAR) which represents the CPU utilization in the form of percentages. The CPU load monitored by SAR is shown in % [EMAIL PROTECTED]:/var/log/sa sar -f sa31|more Linux 2.6.16.21-0.8-default (hostux2) 31/08/07 00:00:26CPU %user %nice %system %iowait %steal %idle 00:01:26all 0.98 0.00 0.53 0.78 0.00 97.70 00:02:26all 0.80 0.00 0.33 0.65 0.00 98.22 How does this % relates to the uptime output? Does this % refers to the run_queue capacity? Is there any way we can modify run_queue. No clue what run_queue is -- are you sure it's part of sar? In SAR's case, is it fair to sum the % of queues (excluding %idle) and conclude that as the total CPU load at that time? The sar numbers are pretty straightforward if you have a grasp of the CPU states. Imagine a system that runs just one program which does the following: 1. Calculate the inverse of a 100x100 matrix 2. Open a file on a floppy disk 3. Write the inverted matrix onto the floppy 4. Sleep for 30 seconds When the program is calculating, the CPU is in user state. When it's opening the file, it makes a call to the kernel and the kernel executes some code related to opening files. At this time (when it's executing kernel code), the CPU is in system state. When the program is writing the file, it's typically waiting for one write to complete (it is blocked) before issuing the next write command. This is iowait state. Idle state is self-explanatory -- the CPU is twiddling its thumbs waiting for someone to give it some work, like when the program above is sleeping. So to sum up: Times when the CPU is executing user code is counted in %user. Times when the CPU is executing a system call (or running any other kernel code) is counted in %system. Times when the CPU is waiting for some I/O to complete is counted in %iowait. Times when the CPU is doing nothing is counted in %idle. Since the CPU must be doing one of these things at any time, the sum of these percentages will always be 100. If you find your CPU is spending a lot of time in iowait, it means your CPU is lying idle because one process (or possibly more) has issued a R/W call, and no other process is ready to run until that R/W completes. You could probably add some comparatively CPU-intensive applications to that system and find little or no degradation in performance since the new applications will soak up CPU iowait time; in other words, the applications will be able to utilise the CPU while other processes are waiting for their R/W to complete. Relationship between CPU states and load averages? Just about the only one I can see is that if your CPU is 100% idle your load average should be 0 :) Regards, - -- Raju - -- Raj Mathur[EMAIL PROTECTED] http://kandalaya.org/ Freedom in Technology Software || February 2008 || http://freed.in/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F PsyTrance Chill: http://schizoid.in/ || It is the mind that moves -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHRPC5yWjQ78xo0X8RAp+wAJ9xVLv6/YH3MnzTZp6FxEEGL3c8PACeKSlX ZCi+9cZaCiH2x4ZVSyW9FUM= =Mi7P -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
On 22/11/2007, Raj Mathur [EMAIL PROTECTED] wrote: [snip] So to sum up: Times when the CPU is executing user code is counted in %user. Times when the CPU is executing a system call (or running any other kernel code) is counted in %system. Times when the CPU is waiting for some I/O to complete is counted in %iowait. I'm not sure I understand this. When a process requests I/O, it is blocked (or removed from ready queue) and CPU moves on to execute next process in the ready-to-run-queue. When the I/O completes, an event wakes up the blocked process(es). A process may be waiting for its I/O while CPU executing some user code. Does this time counted in %user or %iowait? Times when the CPU is doing nothing is counted in %idle. Since the CPU must be doing one of these things at any time, the sum of these percentages will always be 100. [snip] If %user and %iowait overlap, then why is the sum 100? Or, is %iowait the time when there are no processes in ready-queue because all of them are waiting for I/O? I think that is idle time and not iowait time. - Kazim Zaidi Blog: http://tuxplayground.blogspot.com ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
hi all good day i want to a used(6 month) laptop if any one have and want to sell than tellme ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
[ilugd] Thread Hijacking [was:Re: Uptime]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Norat Saraswat wrote: hi all good day i want to a used(6 month) laptop if any one have and want to sell than tellme Now look here Norat, with whatever good intentions you may be having, thread-hijacking [1] is really a bad way to go forward on a mailing list (LUG list or any other). Take some time to compose a new mail and of course try and be a bit polite :) :sankarshan [1] http://www.answers.com/topic/thread-hijacking -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHRRWgXQZpNTcrCzMRAvdAAJ9J2Of0o0lADFCWpba7gyrYwFgqSgCgxD3k TKWdiMhNXtjB2xwHz2rqpgk= =9wEE -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
[ilugd] some thing finding
Hi all i want a used and good condition laptop and not expencive so plz if any one have it plz tell me thanks and warms regards Norat Saraswat ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
Re: [ilugd] Uptime
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 22 Nov 2007, Kazim Zaidi wrote: On 22/11/2007, Raj Mathur [EMAIL PROTECTED] wrote: [snip] So to sum up: Times when the CPU is executing user code is counted in %user. Times when the CPU is executing a system call (or running any other kernel code) is counted in %system. Times when the CPU is waiting for some I/O to complete is counted in %iowait. I'm not sure I understand this. When a process requests I/O, it is blocked (or removed from ready queue) and CPU moves on to execute next process in the ready-to-run-queue. When the I/O completes, an event wakes up the blocked process(es). A process may be waiting for its I/O while CPU executing some user code. Does this time counted in %user or %iowait? When one process is waiting for I/O and another is running in (say) user state, the CPU is actually in user state. That time will be accounted for in %user, not in %iowait. Times when the CPU is doing nothing is counted in %idle. Since the CPU must be doing one of these things at any time, the sum of these percentages will always be 100. [snip] If %user and %iowait overlap, then why is the sum 100? Or, is %iowait the time when there are no processes in ready-queue because all of them are waiting for I/O? I think that is idle time and not iowait time. Nope, that is %iowait time. Idle is when no process is doing anything. If you want to see this in action, do the following on a relatively unloaded system: - - Open up one terminal and run: sar -u 1 1 - - Open up another terminal and run: ls -lR / /dev/null Watch the %iowait times in the sar output go up as ls keeps waiting to read the disk. Now start up some CPU-intensive process like glxgears (GNU Chess is even better) and watch the %iowait times go down. This is because the time ls is spending waiting for I/O to complete is being soaked up by glxgears/gnuchess using up the CPU. Regards, - -- Raju - -- Raj Mathur[EMAIL PROTECTED] http://kandalaya.org/ Freedom in Technology Software || February 2008 || http://freed.in/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F PsyTrance Chill: http://schizoid.in/ || It is the mind that moves -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHRR4IyWjQ78xo0X8RAgiSAJ0T+DJdIV3jlUcFxgN0KI6idAsBEQCfbjdH zPzt1qH4Dwtc7+cgWeNYiKw= =zRlw -END PGP SIGNATURE- ___ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
