Topic: How do I get rid of squid (SME 6.0)?

[herring]

I recently installed SME 6.0.  I'm still finding my way around but like it quite a bit so far.

One thing I am finding is that, with limited memory and a slow drive, running squid is not benefitting me at all.  I would really prefer just a plain ol' internet connection, without caching.

I tried to be smart and remove the squid reference from /etc/rc.d/rc7.d but then internet access works very poorly.

I tried going through the config in the console again but can't find any way to turn it off there.  Is there some way I can ditch squid and have the system still work?

I looked around and found a "squid cache manager", I guess that would let me set the cache to zero?  Is that the only way to do this...I'd rather have it not run at all if I'm not using it.

Thanks!

[arne]

I can't say I remember it 100 % for sure, but I think the 6.0 does work with plain nat by default (?!). If you connect out via port 80 there will be just a "packet natting" while if you access via the squid port (3129) you will pass the trafic via the squid proxy.

I think the Squid proxy will not pull any load from the system as long as it is there as a more or less sleeping process, so there should not be any rason to shut it down.

The 7.0 Beta 5 has a "squid turn on/off function".

I think that if it is for use as a home server the 7.0 Beta 5 is a good choice. For the earlier revisions of 7.0 Beta had a problem that they pulled a rather big load on "poor" hardware while "doing nothing". On the 7.0 B5 this changed so I think it can run rather nice and effective also on "small" hardware.

By the way, I'm using the 7.0 B5 as a gateway in my home now. That's the reason my info about the 6.0.1 is just what I think to remember.

[Brave Dave]

/sbin/e-smith/db configuration setprop squid \
 status disabled
/sbin/e-smith/signal-event console-save
/sbin/e-smith/signal-event reboot

[cc_skavenger]

To disable Transparent HTTP (Squid) Proxy:


/sbin/e-smith/db configuration setprop squid Transparent no
/sbin/e-smith/signal-event remoteaccess-update

[arne]

Does the 6.0 really have a transparant proxy ? I don't know, but I thought the 6.0 I used before did not (??) I notice that the 7.0 B5 I use now has such a feature, that can be turned off.

[cc_skavenger]

yes it does, it is on by default.  the settings are pretty minimal, but it is there.

[herring]

Thanks, guys.  This forum is great!

arne:  yes, squid is certainly running.  It is listed during the startup procedure, and you can find it as a running process.  Or, on my machine, you can just type the address of a large page (like slashdot), hit enter, and listen to the server's drive start to chatter.

davidbray and cc_skavenger:  is there any significant difference between the two sets of commands you've given, IOW any reason I'd use one over the other?

[Brave Dave]

Transproxy will change the masquerade settings

Disabling the service will - disable the service (how else can you say that) - but this will free any memory associated

but transproxy will leave the service for someone who wants to manually enter the settings into the browser.

look at the frragment;
/etc/e-smith/templates/etc/rc.d/init.d/masq/90adjustTransProxy

[cc_skavenger]

/sbin/e-smith/db configuration setprop squid \
 status disabled
/sbin/e-smith/signal-event console-save
/sbin/e-smith/signal-event reboot

The top line tells sme that you want to disable the squid service.  The second line tells sme to rebuild the templates and the last line tells sme to reboot and do its administrative stuff after the reboot.  I do not know if you will be able to use the box as a gateway after these commands.  The commands that I gave simply adjust the firewall settings so that http is not sent through squid but simply go to the browser.  It turns off the redirect to squid.  Squid is still running and can be used if the settings are entered into the browser manually.  
Looking at it, you could use both sets of commands, to turn off the http proxy and to disable the squid service completely.

HTH

[herring]

Yes, that did help.  I chose the commands that just stopped forwarding through squid rather than disabling it, because I don't want to lose the gateway ability...that's the whole point of the machine.

2 more questions:  

1. If I try the commands that disable squid altogether, and it doesn't work as a gateway anymore, could I just replace "disabled" in the first line of commands with "enabled" to put things back the way they were?  I'd rather not have a process running for no reason (I'm just that way).

2. Is there a reference somewhere for this commandset, which seems to be unique to SME server? I have 3 documents in .pdf (6000_tech_handbook, sme_manual and sme_admin_guide) which are useful but do not cover any CLI tasks.

[herring]

BTW, I installed yum and ran the updates last night, so the machine is "current".  So easy, too!

[Brave Dave]

This will show most things
/sbin/e-smith/db configuration show

This will show squid
/sbin/e-smith/db configuration show  squid

Result;
squid=service
    TransparentPort=3128
    status=enabled

Note Transproxy is not shown, but it is available as a setting .. shows most things

Disabling Squid will not disable the gateway; if you look at the earlier mentioned fragment that is clear;

Yes, just replace disabled with enabled to re-enable

[herring]

This will show most things
/sbin/e-smith/db configuration show

This will show squid
/sbin/e-smith/db configuration show  squid

Result;
squid=service
    TransparentPort=3128
    status=enabled

Note Transproxy is not shown, but it is available as a setting .. shows most things

Disabling Squid will not disable the gateway; if you look at the earlier mentioned fragment that is clear;

Yes, just replace disabled with enabled to re-enable

Excellent.  Humming along smoothly now.  Thank you for your help!