On Wed, 2004-02-25 at 11:07, Steve Palmer wrote:

We got one too. If we don't answer it we can be teh summoned! @_@

Looks like they're deadly serious about it anyway.

If they were not serious, they wouldn't be doing a full investigation. It costs them a lot to do an investigation so they don't start it unless they are pretty sure there is a case to answer. The problem for MS is that its not just this country. Schools agreement works in more or less the same way in other countries so if it gets changed here it will also likely have to get changed elsewhere. It surprises me a bit that they don't simply change the agreement to say all computers running any Microsoft products. That would sort it out and make very little practical difference to their current revenue. There are only three reasons why they don't 1.) They believe that the OFT will find in their favour 2.) They are arrogant and think that even if the OFT find against them they will be able to tough it out with delays and other tactics until the problem goes away 3.) They really are paranoid about letting Linux in and would rather fight the OFT than lower the barriers even a small amount. Maybe its a combination of all 3. I guess the only reason the OFT would back off is if in sending out letters to schools, they all say they have no interest in Linux at all and so MSSA is not a consideration in its use. OTOH if even a significant minority say we might have tried Linux but its not worth it because we are on MSSA. The worry is that many schools don't know the implications of MSSA in that they have to pay a license fee annually for any pentium based PC even if its not running MS software. So they may be unaware that they can't use Linux without counting the Linux boxes in the annual total. Like I said, in some ways the monopoly is so entrenched it makes gathering evidence against it more difficult! eg a school might say yikes, if MSSA is declared void isn't this going to put my software costs up? I'd better say nowt. Fact is we don't know what will happen if MSSA is declared void but in the overall scheme of things competition usually forces prices down, it just might not immediately in a particular sector. I hope the OFT realise how complex and far-reaching this monopoly is. If anyone would like to make these or any other comments the E-mail address of the investigating officer is edward.anderson@oft.gsi.gov.uk. Other contact details are Mr E Anderson Principal Case Officer Media, Sports & Information Industries Office of Fair Trading Fleetbank House 2-6 Salisbury Square London EC4Y 8JX Tel: 020 7211 8343 Fax: 020 7211 8354 Regards, -- ian

Having upgraded our Suse box to V9 (new install) and re making Squid/2.4.STABLE7 we can only run squid from the supplied script in the \bin folder, If we try say -k rotate . we ge a message to say that it canot find Squid! This is the same in root, either from the commad window with the path set to \sbin or by clicking the icon in \sbin! Any ideas anyone? Kind regards Adrian

"\" "/" I used the right one! :-) In the /bin folder is a script that will start squid - it works! and is running now. The squid exe lives as it should in /sbin When I compiled I used ./configure --enable-arp-acl --enable-delay-pools make make clean make install Not sure that I needed the "make" AND the "make clean" but did it anyway... I'm sure it is a path problem but clciking on the icon in KDE does not work either.

From the shell konsole..

set path to /usr/local/squid/sbin then squid -k rotate returns... command not found If I click /usr/local/squid/sbin/squid from my desktop I get "couldn't find the program 'squid'" ----- Original Message ----- From: Thomas Adam To: adrian.wells ; Sent: Friday, February 27, 2004 1:46 PM Subject: Re: [suse-linux-uk-schools] Squid Starting Problem

--- "adrian.wells" wrote:

...

Having upgraded our Suse box to V9 (new install) and re making Squid/2.4.STABLE7 we can only run squid from the supplied script in the \bin folder, If we try say -k rotate . we ge a message to say that it canot find Squid!

Directory delimiters begin /bin

with the forward slash going "/" way as opposed to DOS which goes "\".

...

This is the same in root, either from the commad window with the path set to \sbin or by clicking the icon in \sbin!

Any ideas anyone?

So:

/bin/squid

is the file you're using? Hmm, that is not correct -- it should not have been installed there at all. If you built it yourself, then it ought to have gone in /usr/local/bin, unless you supplied something different to ./configure --prefix, but I am assuming you did not.

Could you be a little clearer as to what you did, and *how* you compiled/installed squid. I think you've made a mistake somewhere. As for "squid -k rotate" not working, this is either a PATH issue, or you have missed something vital off when you installed it.

-- Thomas Adam

===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net

"<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)"

-- Benjamin A. Okopnik (Linux Gazette Technical Editor)

___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

Thanks for clearing up the 'make' & 'make clean' Thomas, It so happens that we compiled it twice, I did it, went off to do something and my technician did it too! so I assume that we ended up with a 'clean' compile anyway. I've also posted this question on the Squid list as I was unsure if it was a Squid or SuSE problem. Marc Elsen asked me to try ./squid -k rotate, not sure what it does, but it works :-) At least I can rotate now as the logs were getting a tad big. If it's of help the file permissions are as follows from / to /sbin/squid User "Read, Write, Execute" Group & Others "Read, Execute" owner root Adrian ----- Original Message ----- From: Thomas Adam To: adrian.wells ; Sent: Friday, February 27, 2004 2:53 PM Subject: Re: [suse-linux-uk-schools] Squid Starting Problem

--- "adrian.wells" wrote:

...

"\" "/" I used the right one! :-)

In the /bin folder is a script that will start squid - it works! and is running now.

The squid exe lives as it should in /sbin

When I compiled I used

./configure --enable-arp-acl --enable-delay-pools make make clean

make clean is ONLY done before "make" so that old compiled files are removed. The order of operation then is:

make clean && make && make install

...

I'm sure it is a path problem but clciking on the icon in KDE does not work either.

...

From the shell konsole..

set path to /usr/local/squid/sbin then squid -k rotate

returns... command not found

If I click /usr/local/squid/sbin/squid from my desktop I get "couldn't find the program 'squid'"

Look inside this script, and then determine where it thinks the squid binary is.

-- Thomas Adam

===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net

"<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)"

-- Benjamin A. Okopnik (Linux Gazette Technical Editor)

___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com

The fact that your technician did that is a little worrying :) He's was just keen to see it working and thought he's surprise me! :-)

It's neither. It's more to do with an uncertainty about compiling apps. ./ means the current directory. The one that you are in. Since "." (the . == current dir) cannot be in $PATH due to security reasons you have to use it. I am interested to see which directory you are in when you issued the: ./squid I was in /usr/local/squid/sbin Strange eh? because a normal squid -k rotate fails!

command. Type in "pwd" before you do it again.

Set up a cronjob to do it. I will when the command works again!

I can't remember now why I updated, oh yeah, 7.2 is no longer suported. A funny bloke with specs keeps doing that to me too! :-) I'll try the pwd on monday, the w/e beckons now :-) Thanks for your help Have a good one Adrian

--- "adrian.wells" wrote: > Hi again,

...

./squid As I said that was from

/usr/local/squid/sbin

...

command. Type in "pwd" before you do it again. This returned the same path. The command would not work unles I used ./

Yes. In that case in /etc/profile.local (create it if it does not exits), add the following (as root): --------------------- #!/bin/sh export PATH=$PATH:/usr/local/squid/sbin ---------------------- save the file, and: chmod o+r /etc/profile.local source /etc/profile.local Then run you squid binary, and it will work fine. HTH, -- Thomas Adam ===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net "<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)" -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

--- "adrian.wells" wrote:

Ha! Thanks :-) I've just been looking on the web for hints on how to do this :-)

This was never a problem before, is it to do with the SuSE version change? 7.2 to 9 ?

No, this is to do with the fact that when you compiled squid, you should have done: ./configure --prefix=/usr/local --exec-prefix=/usr/local/bin For some reason. the Makefile for squid, assumes a non-standard default prefix. Not a problem though, it's sorted :) HTH, -- Thomas Adam ===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net "<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)" -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

chmod o+r /etc/profile.local source /etc/profile.local

Should that have been chmod +o+r /etc/profile.local ? Because without the + I get a too few parts error, with the extra + it ran without error. Anyway, rotate etc. work now :-) I tried adding /ACLs in a similar way, as this is where I like to keep my acl text lists away from the squid.config file, but it did not appear to work, any idea why. Squid reports that it can't find the specified file which I'd (now) expect! What is the point of a fully qualified address if it's ignored?

Then run you squid binary, and it will work fine. See above :-)

Thanks Adrian

...

I tried adding /ACLs in a similar way, as this is where I like to keep my acl text lists away from the squid.config file, but it did not appear to work, any idea why. Squid reports that it can't find the specified file which I'd (now) expect! What is the point of a fully qualified address if it's ignored?

I'm not quite understanding you, Adrian. What did you try to do? Where did you add /ACLs? I need a little more clarity and information.

That's right, mock the afflicted! :-) I usually keep my text files containing the acl data in a folder called 'ACLs' in the root folder, so in my squid confign I would have the line... acl ICT arp "/ACLs/ICT.txt" acl BadExtn url_regex -i "/ACLs/BadExtn.txt" etc. Pointing to the list of ICT department computer MAC addresses etc. This worked fine before, but does not work now! as Squid says it can't find the files! So I have edited my squid.config and placed the ACL lists in the same folder as squid.config (I generate all of the ACL lists and the squid.config from a database that allows me to group computers and apply times, baned lists, allowed lists etc.). I keep the files seperate because I like to keep things tidy. Adrian

I tried adding /ACLs in a similar way, as this is where I like to keep my acl text lists away from the squid.config file, but it did not appear to work, any idea why. Squid reports that it can't find the specified file which I'd (now) expect! What is the point of a fully qualified address if it's ignored?

Our ACLs, for example, are acl local-servers dstdomain felsted.essex.sch.uk acl whitelist dstdomain "/usr/local/etc/squid/whitelist" acl adsl-types urlpath_regex -i "/usr/local/etc/squid/adsl-types" acl bad-sites dstdomain "/usr/local/etc/squid/bad-sites" acl badstar-sites url_regex -i "/usr/local/etc/squid/badstar-sites" acl bad-types urlpath_regex -i "/usr/local/etc/squid/bad-types" acl webmail dstdomain "/usr/local/etc/squid/webmail-sites" acl webmailstar url_regex -i "/usr/local/etc/squid/webmailstar-sites" acl webmailtimes time "/usr/local/etc/squid/webmail-times" acl msnmessengersites url_regex -i "/usr/local/etc/squid/msnmessenger-sites" acl msnmessengertimes time "/usr/local/etc/squid/msnmessenger-times" acl staffhosts srcdomain "/usr/local/etc/squid/staffhosts" acl pupil_pcs srcdom_regex pupil* http_access deny bad-sites !staffhosts http_access deny badstar-sites !staffhosts http_access deny msnmessengersites !msnmessengertimes !staffhosts and the file adsl-types is \.wma$ \.zip$ \.mp3$ \.lzh$ \.exe$ \.rar$ \.pdf$ \.wmv$ while the file badstar-sites is .*bonkablebeauties.com .*rathergood.co.uk -- Christopher Dawkins, Felsted School, Dunmow, Essex CM6 3JG 01371-822698, mobile 07816 821659 cchd@felsted.essex.sch.uk