When I was experimenting with Apache it would show up in ps as "httpd" not
"Apache".
-Original Message-
From: Kevin Coyner [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 07, 2004 10:18 AM
To: [EMAIL PROTECTED]
Subject: Re: apache won't start although no errors
On Sat, Feb 07, 2004
Excellent!
Thanks for the post.
John
-Original Message-
From: Colin Watson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 23, 2004 4:45 PM
To: Debian Users List
Cc: Antonio Rodriguez
Subject: Re: Bruce Perens talks to BBC
On Fri, Jan 23, 2004 at 04:41:33PM -0500, Antonio Rodriguez wro
Yep. Kind of amazing. Thanks for the post.
-Original Message-
From: Bill Moseley [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 5:29 PM
To: [EMAIL PROTECTED]
Subject: SCO: The threat to our national security
Sorry if this is old news or already posted and to those burned ou
Good Morning,
My Debian box provides DNS, Firewall, and NAT for my home network like I
think you're planning to do. The HOWTO's are a great place to start but you
need to read (or at least scan) the BIND, IPTABLES, etc. documentation as
well and don't forget the README.Debian. Many of the HOWTO'
I'd like some more details. Are you connecting to the windows domain via
vpn?
John Purser
-Original Message-
From: Anand Atreya [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2003 3:03 PM
To: [EMAIL PROTECTED]
Subject: Joining a windows domain from behind a debian NAT box
Hi,
I ha
init.d
On Mon, 2003-08-18 at 21:37, John M. Purser wrote:
> Good Morning,
>
> A few days ago I installed Samba on my Woody box. All was well for a
couple
> of days then smbd stopped running with an error message that said port 139
> was already in use. With help from this group I
Thanks Nate. fuser worked perfectly.
What it turned out to be was inetd watching the port so it could run samba
on demand. Unfortunatly Samba was also in the run level scripts. I
installed from the .deb using stable sources so I'm kind of puzzled about
how this happened and why it worked at fir
Good Morning,
A few days ago I installed Samba on my Woody box. All was well for a couple
of days then smbd stopped running with an error message that said port 139
was already in use. With help from this group I tracked down inetd as the
culprit and sure enough there were lines to start Samba i
I apologize. I know this was a thread a while back and I believe it was on
this mailing list but now I can't find it. I'm getting this error message
from samba:
[2003/08/17 12:15:26, 0] lib/util_sock.c:open_socket_in(789)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already
] [mailto:[EMAIL PROTECTED] Behalf Of
Stephen Patterson
Sent: Monday, August 11, 2003 4:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Name resolution on a dual homed host
On Sun, 10 Aug 2003 22:20:10 +0200, John M. Purser wrote:
> I've got a Debian woody box acting as firewall for a small home
Hello,
My /var/log/messages has a lot of lines that look like:
Aug 12 08:29:55 lan named[244]: client 192.168.1.10#2083: update
'1.168.192.in-addr.arpa/IN' denied
Aug 12 08:34:55 lan named[244]: client 192.168.1.10#2094: update
'1.168.192.in-addr.arpa/IN' denied
The client involved is my win2k m
I got similar errors from kde using an internal name. The problem was dns
resolution as the dhcp client was over writing my resolv.conf. Bottom line,
the place(s) you told your computer to look for addresses didn't come up
with one for that name.
I'd say you could run your own dns server making
message: update '1.168.192.in-addr.arpa/IN'
denied
On Tue, 2003-08-12 at 15:46, John M. Purser wrote:
> Hello,
>
> My /var/log/messages has a lot of lines that look like:
>
> Aug 12 08:29:55 lan named[244]: client 192.168.1.10#2083: update
> '1.168.192.in-addr.arpa
Hello,
I've got a Debian woody box acting as firewall for a small home network. It
has two ethernet cards with the internal network one being static and the
external one configured by DHCP. I use a cable modem for internet
connectivity. I'd like the Debian box to use the dns server it's running
In my zone files I wrote the addresses in the "A" records as 192.168.1.41.
with a trailing period. I was sure that was right so never questioned it.
Removing the last period fixed everything.
Thanks to all who replied.
John Purser
-Original Message-----
From: John M. Purser [mai
Ooooh! A blanket call for opinions! Finally a letter I'm qualified to
respond too!
I got on Woody when it was testing because a project I was involved with was
using it. We had several people from HP on the project and too a man their
Unix was Debian. It was my introduction to Debian. About a
x27;ll go back to the documentation again to see
what I can see.
John Purser
-Original Message-
From: Richard Lyons [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 03, 2003 4:11 AM
To: [EMAIL PROTECTED]
Subject: Re: Bind9 on Woody - "Bad dotted quad"
On Saturday 02 August 2003 23
I've installed the bind9 package and tried to configure it to work with my
little internal network. When I start it up I get an error message telling
me "bad dotted quad" saying it's from the zone configuration file for my
network which uses the 192.168.0 network numbers. When I replace this with
18 matches
Mail list logo