Re: [wccpd-devel] kernel wccp support

[Blues <bl...@ds...>]

On 29 Jan 2002, Eduardo J. Blanco wrote:
>     Few reflections:
>     - location of scripts - I don't know where should it be, maybe in=20
>     /etc/wccp/scripts ?
> Sigh... I don't specially like scripts under /etc (yeah, I know,
> /etc/rc.d).  What does the FSSTD has to say about it?  IIRC, GNU tends
> to use /usr/libexec for that.

I'll look at that in  some free time.

This is strange thing...=20
1. This can be changed to make something work otherwise (esp. other marks=
) =20
-> /etc/......
2. like other scripts it can be run-by-hand by root -> /usr/sbin
3. Maybe standards(TM) are talking something about this kind of files?
4. I really shure it  shouldn't be in /usr/lib/wccpd - this is not any=20
library.

...so... maybe move it to /var/lib/wccpd ? AFAIR FHS says that there=20
should be any of program datas.

From _user_ point the best thing would be /usr/sbin ....

Am I making to much flame ? ;)

>     - dc called in scripts - ugly :)
> Agreed.  Any way to convert a decimal number to hex or viceversa?  ip
> rule, iptables and the like all differ slightly on what they expect. :-=
(
>     - all caches should be called from some configuration file (maybe i=
n=20
>     /etc/wccp/wccpd.conf.
> Sorry, I don't understand this... Do you want a config file to list the
> valid caches?

This 2 thing are connected (in my mind ;)
I think that wccpd should call all of the externel programs (ip, ipvs).=20
Only iptables/ipchains should stay for the end-user.
Now - if it will be done (should, I think...):
1. one config-file will drive everything. eg. config:
cache {
	server proxy1.bla.bla.pl;
	wccp-protocol 1;
	encapsulation gre;
	fw-mark 0x80;
}
2. scripts location will be no problem anymore (no scripts :)  )
3. system log will be more reliable - now only connection of new cache is=
=20
noticed. Disconnection isn't. Some diagnostics can be made...? :)

Sure - almost everything can be done by smarter script, but... its not=20
"clean" solution. Point 3 can't be done in current model.

Disadvantages of making it that way:
- it will be external-programs-dependent
- no easy way to change proxies on-fly. Solution of that can be some=20
socket or something like that + some small external program for=20
management.

Is it clear?

>     For now it looks OK. It's "raw" but works fine.
>=20
> Ok; I'll see to it.  I'm working now on WCCP v2.=20

I'm waiting :)

--=20
---------------------------------
pozdr.  Pawe=B3 Go=B3aszewski       =20
---------------------------------
CPU not found - software emulation...