We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

perldoc...


Myatu
29-01-2010, 09:20
It's back up again, though I finished the script already Nothing is straight forward with Perl... Scalars... Non-Scalars... 304 different ways to do the same darn thing... No wonder I didn't bother with it ages ago, but Proxmox uses it quite a bit

freshwire
28-01-2010, 18:05
downforeveryoneorjustme.com was down yesterday

Razakel
28-01-2010, 18:04
Quote Originally Posted by Myatu
Thanks! At least it isn't just me then (hard to tell lately with all the stuff I'm doing). That sucks...
http://downforeveryoneorjustme.com/

:P

Myatu
28-01-2010, 12:42
Thanks! At least it isn't just me then (hard to tell lately with all the stuff I'm doing). That sucks...

HandsomeChap
28-01-2010, 12:12
Lol why does a timing out tracert mean you can ping it?

I cannot ping it and my tracert also times out after a few hops:


Code:
>ping perldoc.perl.org

Pinging x4.develooper.com [207.171.7.64] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.171.7.64:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Code:
>tracert perldoc.perl.org

Tracing route to x4.develooper.com [207.171.7.64]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  gw.nikken.lan [192.168.3.1]
  2     2 ms     3 ms     2 ms  router.nikken-world.com [217.12.148.21]
  3     8 ms     8 ms     8 ms  er2.tcw.peerex.net [217.12.147.6]
  4     9 ms     7 ms     7 ms  5-i5-sw1.tcw.peerex.net [217.12.147.65]
  5     7 ms     8 ms     8 ms  bn-br1.tcw.peerex.net [217.12.144.68]
  6     7 ms     7 ms     7 ms  peerex-gw.cust.telecomplete.net [213.160.121.21]

  7    13 ms    14 ms    15 ms  v951-r1.tch.telecomplete.net [193.0.255.198]
  8    14 ms    14 ms    15 ms  v101-r4.thn.telecomplete.net [213.160.96.121]
  9    14 ms    14 ms    14 ms  v100-r5.thn.telecomplete.net [213.160.96.49]
 10    14 ms    14 ms    15 ms  ge1-0.ar2.lon2.gblx.net [195.66.224.112]
 11   161 ms   162 ms   162 ms  Phyber.po1.1200.ar4.LAX1.gblx.net [208.49.125.18
6]
 12   162 ms   163 ms   162 ms  perl-foundation.vl137.cr01.lax1.phyber.com [207.
171.2.195]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17  ^C

marks
28-01-2010, 11:52
yes

[marks@ns3434343 ~]# traceroute perldoc.perl.org
traceroute to perldoc.perl.org (207.171.7.64), 30 hops max, 40 byte packets
1 94.23.16.254 (94.23.16.254) 216.119 ms * *
2 * * *
3 80g.th2-1-6k.routers.chtix.eu (213.186.32.166) 11.240 ms * *
4 80g.gsw-2-6k.routers.chtix.eu (213.186.32.162) 4.360 ms * *
5 30g.gblx.gsw-1-6k.routers.chtix.eu (213.186.32.249) 4.293 ms 4.304 ms 4.328 ms
6 Phyber.po1.1200.ar4.LAX1.gblx.net (208.49.125.186) 141.918 ms 141.767 ms 141.809 ms
7 * * *
8 * * *
...

Ashley
28-01-2010, 11:20
Still down

yatesco
28-01-2010, 10:01
Nope (from Leicester UK)

Myatu
28-01-2010, 08:57
Quick Q: can anyone reach http://perldoc.perl.org ?