Hi,
Zentek International does provide such a service using Debian servers.
If you would like more information, just mail me directly at
[EMAIL PROTECTED]
As for the availability of other companies using Debian, i can tell you
that you'd be hard pressed to find even a handful. I think they use Re
Hi,
Zentek International does provide such a service using Debian servers.
If you would like more information, just mail me directly at
[EMAIL PROTECTED]
As for the availability of other companies using Debian, i can tell you
that you'd be hard pressed to find even a handful.
I use nextvision.net a
Hi!
I get the following error messages in my log:
Apr 9 06:47:39 ns tcp-env[17281]: warning: /etc/hosts.allow, line 11: can't
verify hostname: gethostbyname(114.trusted.net) failed
Apr 9 06:47:40 ns tcp-env[17281]: refused connect from 209.140.0.114
Apr 9 06:56:54 ns tcp-env[17346]: connect f
I checked the communitech.net website... such as at their dedicated server
webpage
(http://www.communitech.net/hosting/dedicated/unix/packages.cgi )
and they all stated they run Redhat 6.1.
Maybe you could direct us to the correct webpage for debian hosting?
Actually... are they one and the same
hello,
were trying oto debug this _big_ PERL web application (lots of forms, etc,
whatever) and it seems like were really lost w/ its code.
is there any way that you can do a line by line trace when a PERL code is
executed on the web that way, we'll have some idea w/c goes where ?
thanks
From: "Chad A. Adlawan" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 10, 2000 1:30 PM
Subject: tracing a PERL cgi script
> hello,
>
>were trying oto debug this _big_ PERL web application (lots of forms,
etc, whatever) and it seems like were really lost w/ its code.
>is there any way that
Typing away merrily, elyograg produced the immortal words:
> I was thinking about this recently, and here's what I reasoned (but have
> never put to the test). Due to the way that reverse DNS works, what would
> have to happen is whatever body gave you the address space would have to
> actually
Typing away merrily, Robert Ruzbacky produced the immortal words:
> Apr 9 06:47:39 ns tcp-env[17281]: warning: /etc/hosts.allow, line 11: can't
> verify hostname: gethostbyname(114.trusted.net) failed
> Apr 9 06:47:40 ns tcp-env[17281]: refused connect from 209.140.0.114
> Apr 9 06:56:54 ns tcp
I checked the communitech.net website... such as at their dedicated server
webpage
(http://www.communitech.net/hosting/dedicated/unix/packages.cgi )
and they all stated they run Redhat 6.1.
Maybe you could direct us to the correct webpage for debian hosting?
http://www.communitech.net/hosting/dedic
or better frozen or stable ?
I think that would work quite well. Just make sure to upgrade the system
regularly. That will keep you abreast of all the problems and allow for a
nice system.
On Mon, 10 Apr 2000, Jaume Teixi wrote:
> or better frozen or stable ?
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a
Typing away merrily, Chad A. Adlawan produced the immortal words:
>were trying oto debug this _big_ PERL web application (lots of forms, etc,
> whatever) and it seems like were really lost w/ its code.
>is there any way that you can do a line by line trace when a PERL code is
> executed o
Typing away merrily, John Haggerty produced the immortal words:
> I think that would work quite well. Just make sure to upgrade the system
> regularly. That will keep you abreast of all the problems and allow for a
> nice system.
Customers can complain quite loudly when something which used to wor
Is there a good example of something in debian breaking a general
script/program server side?
On Mon, 10 Apr 2000, Phil Pennock wrote:
> Typing away merrily, John Haggerty produced the immortal words:
> > I think that would work quite well. Just make sure to upgrade the system
> > regularly. That
Typing away merrily, John Haggerty produced the immortal words:
> Is there a good example of something in debian breaking a general
> script/program server side?
Not that comes to mind.
But what happens when, eg, perl is upgraded to 5.6? The perl4 -> perl5
transition broke enough stuff. Will th
Then you could have the solution of say changing the name of the package
to perhaps reflect that in fact you have perl4 or something and just
install incremental upgrades for the packages that aren't prone to
breakage. Eventually as people upgrade their stuff. You could slowly
retire the old stuff
We run unstable and make a point of upgrading frequently.
It is our job as ISP to maintain the environment and make
improvements. We tell our clients that old scripts will break
as that environment changes. Either they pay us to maintain
the scripts or they take it on themselves.
The most r
Typing away merrily, John Haggerty produced the immortal words:
> Then you could have the solution of say changing the name of the package
> to perhaps reflect that in fact you have perl4 or something and just
> install incremental upgrades for the packages that aren't prone to
> breakage. Eventual
Typing away merrily, [EMAIL PROTECTED] produced the immortal words:
> You **need** clients to complain loudly when something breaks; otherwise
> how will you know? As for the lawyers, you'll hear from them
> if you upgrade or if you fail to upgrade. ;^) We've just found
> it easier to maintain
Is there say a test that can be implimented that would test to determine
wheather the program you are running will work under perl and
then pick that version of perl? That would really rock and would possibly
be quite easy considering perl is a great tool for text manipulation and
analysis.
On Mon
On Mon, 10 Apr 2000, John Haggerty wrote:
> Is there a good example of something in debian breaking a general
> script/program server side?
In the past, the upgrade of libmysqlclient.so.6 caused grief for most
packages that version-depended on libmysqlclient.so.4. Having a
non-production compute
On Mon, Apr 10, 2000 at 07:01:04PM +0200, Phil Pennock wrote:
> Typing away merrily, [EMAIL PROTECTED] produced the immortal words:
> > You **need** clients to complain loudly when something breaks; otherwise
> > how will you know? As for the lawyers, you'll hear from them
> > if you upgrade or i
Typing away merrily, John Haggerty produced the immortal words:
> Is there say a test that can be implimented that would test to determine
> wheather the program you are running will work under perl and
> then pick that version of perl? That would really rock and would possibly
> be quite easy cons
Typing away merrily, [EMAIL PROTECTED] produced the immortal words:
> So perl is perl4. That creates problems for users typing in perl and
On one service, yes. But that service predates perl5.
Upgrading the hardware for Y2k was fun - when was the last time that you
tried finding the source for
One of the most interesting things that actually got me charmed with
debian was a copy of debian 0.99beta that I had on some old cds. I
remember that day well. There were some problems and some functionality
missing but overall it's useful. I could install almost everything in the
distribution on m
Typing away merrily, John Haggerty produced the immortal words:
> If you need source that badly or ever need it in the future just get some
> copies of everything and burn some CDs for permanent archival storage. You
> can't go wrong there.
We've now made sure that it's on a central CVS server in
On Mon, Apr 10, 2000 at 07:15:40PM +0200, Phil Pennock wrote:
> Typing away merrily, John Haggerty produced the immortal words:
> > Is there say a test that can be implimented that would test to determine
> > wheather the program you are running will work under perl and
> > then pick that version o
Typing away merrily, [EMAIL PROTECTED] produced the immortal words:
> Actually, all of the scripts we maintain do "register" their existence
> and location in syslog each time called.
Interesting. Why not just parse the server logs?
> This is not just a perl issue. What about header files, /usr
On Mon, Apr 10, 2000 at 10:28:27AM -0400, John Haggerty wrote:
> Is there a good example of something in debian breaking a general
> script/program server side?
SSH.
Best regards,
Daniel
29 matches
Mail list logo
