How do I resolve a "request timed out" when pinging?
Request timed out means that the host you’re pinging might be:down or unreachable (e.g. because it’s on a different network/subnet, it’s shut down, etc.)behind a firewall that drops your ICMP echo request packetsthe ping command has been disabled for that network by the syadminYou have no Internet connection/network connectivityall of the above.To rule out Internet connection problems, ping Google or 8.8.8.8 (Google DNS) and you should get a successful response.If this is not the case, something’s wrong (network cable disconnected, incorrect network adapter drivers, connection to the ISP down, NIC not working correctly, etc.).Ping localhost (127.0.0.1) to make sure your NIC card works correctly.You should ping the gateway set up for your computer, as well.If it’s the correct one, you should be able to reach it.Also, you can get a better understanding of the situation by running the traceroute command (tracert, in Windows) on that IP address you want to reach, if you’re lucky and the admin allowed it through the firewall.In fact, that command’s often disabled, as it can be used for network recon purposes.With traceroute you can view the whole route packets go through from your endpoint up to the final endpoint and you can understand on which specific hop there are issues.When some hops have issues, you’ll see a bunch of asterisks and packets are eventually dropped.In the below example, you see issues start at hop no. 23.Additionally, run ipconfig /all and have a look at your IP configuration (subnet mask, gateway, etc.).If the IP address you want to ping has a different subnet mask or gateway than yours does, then it’s on a different subnet and you can’t reach it, unless you have another network adapter configured with those specific network parameters.
Why don’t we have a universal time and date system? Could we create one?
If you mean “universal” in the sense that all humans on Earth use it, then we already have such a thing, it's called UTC.If, instead, you mean “universal” in the sense that it could used anywhere in the universe, I'm afraid such a thing is impossible. The rate of the passage of time depends on where you are and how fast you're moving, together known as a reference frame. This is one of the fundamental revelations of special and general relativity. In fact, two reference frames can't even agree whether two events occurred simultaneously or not, so we can't set some agreed-upon external source of time.When the reference frames are very close (such as within the solar system) then it's much easier to synchronise clocks. Even though the time of GPS satellites runs slightly faster than on Earth the difference is small enough that we can compensate for it. Similarly a Mars colony will want their own calendar and clock system (the Martian day is about 30 minutes longer than an Earth day, but its year is about 50% longer), but they'll be in almost constant contact with Earth and will likely use UTC alongside their local time and date.
I need an explanation with GMT, EST, UTC, timezone related?
Suppose you are standing on the North Pole, sometime in the summer so that the sun is above the horizon. You see the sun in front of you, and observe it moving to the right. All the meridians merge under your feet, and the sun will cross them in turn, moving fifteen degrees each hour. It will be local solar noon under the sun; as the sun moves, so will noon. It is clear that time, as defined by the sun, will vary from place to place, and that to make time more manageable, a zone system, in which all clocks in a zone would be similarly set, would be useful. The basics of the design are: - There is a prime meridian, against which all other meridians are measured. By convention, it runs through the Naval Observatory in Greenwich, England. - There must be a meridian at which the day begins. At any given time, there must be times at different places belonging to two different days. The boundary, which mostly follows the 180 meridian but has some wiggles for some island groups, is the International Date Line. - The original universal time was Greenwich Mean Time. Because the earth's orbit is not quite circular, the duration of the time between succesive solar noons varies throughout the year. GMT is contrived to flatten the bumps, so that the sun is at the same place at the beginning of each year. It has been supplanted by Universal Coordinated Time, because there are irregularities in the earth's rotation and the desired accuracy can be had only with special clocks, which keep time precisely to a few parts in a trillion. Because the earth's rotation is slowing due to the tides, a leap second is added to the UTC about once a year. The various time zones can be designated by the difference between them and GMT or UTC. Eastern standard time is five hours earlier than GMT, or GMT-5. Pacific Standard Time is GMT-8. Paris and Berlin are on GMT+1. By subraction, we can find that the difference between EST and Paris time is 6 hours.
How can I display a notification at driver dashboard after customer request for taxi travel and notification should display in seconds PHP MySQL?
book customer booking into DB using UTC, then using front-end JS AJAX grab the value, but translate into user timezone. Then just increment on the client, and when the vehicle arrives have it send another event which can be converted and logged to UTC, giving you travel time. The best part is any client should be able to count from a time for a very long time, until taxi gets to client...
What are some of the Unix/Linux scripts you use every day?
I keep two scripts, first to backup extremely important data and the other one for other important files. And the script is very simple:rsync -r /home/nikhil/
What are good examples of an email to send when an IT platform is scheduled to be unavailable because of an update?
Here is a typical notification that we would use:Subject: SCHEDULED SYSTEM DOWNTIME - 12 Nov 2014Dear Network User,Please be advised that the network will be unavailable from 01:00am to 05:30am on November 12th, 2014. This period of downtime will be scheduled for necessary updates to be applied to the network servers.We apologise for the inconvenience that this may cause. Kindly inform the IT Service Desk (at ext. 1234) of any concerns that you may have about the planned outage.Kind regards,Dilbert TruemanNetwork Administrator.The following factors are important:1. Give at least 48 hours notice, wherever possible. For updates, this should be predictable. Follow up with 12 hour and 1 hour notifications as well. Not everybody has this as a "To Be Remembered" mental priority.2. Always schedule maintenance/updates/upgrades for the least inconvenient time for your users. Inconveniencing your technical guys, compared to inconveniencing the entire business should persuade you.3. Be specific about the time and date - no ambiguity - and allow yourself at least 20% excess time. Also be specific about the format that you display the time and date - do not rely on local conventions (i.e. the conventions of the person writing the notification).4. ALWAYS give a contact number for inquiries, in any notification. If you don't have a service desk/help line/generic call center, then provide the contact name and number of an informed(!) person. 5. It is counter-productive to swamp the recipient of the notification with technical details or blow-by-blow accounts of what is planned to be done. But DO give a brief description (your users are human beings, after all) that will satisfy their basic concerns. The email SUBJECT line must be clear and informative. It should say just enough to be a reminder without the message having to re-read by a forgetful recipient.5. Be polite and err on the side of being apologetic, if you are uncertain about the tone of your notification. Compose your notification as if the CEO is going to read it. You provide a service, you are not the customer, so never sound like a dictator.6. In the above example, you should obviously replace "Network User" and associated references with the name or identity of the service which will be affected. For wide-scale outages, say "Dear IT Systems User". For (a) specific system/s; name that/those system/s. Eg: "Dear Sales, Dispatch and Receiving Systems users".