Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Dec 2003 02:16:45 +0100
From:      Melvyn Sopacua <freebsd-questions@webteckies.org>
To:        Marty Landman <MLandman@face2interface.com>
Cc:        FreeBSD-questions <questions@freebsd.org>
Subject:   Re: apache has fallen [and it won't get up]
Message-ID:  <200312010216.50694.freebsd-questions@webteckies.org>
In-Reply-To: <6.0.0.22.0.20031130190217.01ba5178@pop.face2interface.com>
References:  <6.0.0.22.0.20031130132339.0773a440@pop.face2interface.com> <200311302120.40443.freebsd-questions@webteckies.org> <6.0.0.22.0.20031130190217.01ba5178@pop.face2interface.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Monday 01 December 2003 01:39, Marty Landman wrote:


> >I think typing:
> >host delliver.mshome.net
> >
> >*on that machine* doesn't give a valid ip address or an adress that is not
> > on the workstation.
>
> Actually I got the corrent ip's for each of my four windoz boxes by
> querying each with their name on mshome.net.
>
> >Since you're refering to 'ics' I guess you're gateway is an MS box and
> >doesn't
> >run DNS or a DNS forwarder at best.
>
> Right, I think. It's a windoz xp home edition box getting dns via dial-up.
> At least I think I'm saying that correctly.

I checked your original message again. It says something about some 
SwamiSalami hostname. Is that by any chance the 'ServerName' of the main 
server? That is what mod_unique_id is trying to resolve. If no ServerName is 
set, it takes the hostname of the computer.

> The apache manual entry for mod_unique_id didn't say a whole lot. This must
> be a default and I wonder if it's something I will eventually miss. What's
> it do, or can you point to a more in depth explanation I can read?

It creates a unique id for every request. This is used by mod_usertrack to 
generate a session id.

There are some other modules that also use this feature, but I can't think of 
any off-hand. It's also convenient if you use an log-analyzer that checks 
whether there are duplicate lines. You can log the created id in a separate 
field and thus make sure that "the same file requested twice within a second, 
from the same host, by the same browser" (think "/images/spacer.gif") is 
something else then "a duplicate logline in the file".

In a nutshell: if you don't care about mod_usertrack or wrongly detected 
duplicate loglines, you have no use for mod_unique_id. Any other apache 
module requiring it, will complain soon enough, but since you have it running 
without - you seem to have no such dependency.

-- 
Melvyn

=======================================================
FreeBSD sarevok.webteckies.org 5.2-BETA FreeBSD 5.2-BETA #1: Sat Nov 29 
00:15:33 CET 2003     root@sarevok.webteckies.org:/usr/obj/usr/src/sys/
SAREVOK_NOFW_DBG  i386
=======================================================

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/ypaCOv9JNmfFN5URAs0XAJ92yd0HNnmpwXc214MbWYtIGGbiYgCgk333
Kb2N5gRFfAG79JlOsL0O/yY=
=IYjo
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312010216.50694.freebsd-questions>