i am trying to configure squid as a non root user .... i compiled using
./configure -prefix=/(path)

now i made binaries using make all and then make install ....
i am getting 2 errors ..

any1 plz suggest me how to configure it appropriately..


/bin/sh ../cfgaux/mkinstalldirs ~csd01420/.sawfish/squid//bin
/usr/bin/install -c RunCache ~csd01420/.sawfish/squid//bin/RunCache
/usr/bin/install: cannot create regular file `/nfs/megh2/csd01420/.sawfish/squid//bin/RunCache': No such file or directory
/usr/bin/install -c RunAccel ~csd01420/.sawfish/squid//bin/RunAccel
/usr/bin/install: cannot create regular file `/nfs/megh2/csd01420/.sawfish/squid//bin/RunAccel': No such file or directory
make[2]: *** [install-binSCRIPTS] Error 1
make[2]: Leaving directory `/nfs/megh2/csd01420/prolog/sml1/squid-2.5.STABLE3/scripts'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/nfs/megh2/csd01420/prolog/sml1/squid-2.5.STABLE3/scripts'
make: *** [install-recursive] Error 1

this is the error i get

I find the idea of trying to run squid
of an nfs-mounted drive rather strange :)

Cheers,
Tink

is it not advisable or what ? i cant understand ....

Well, think about it... 1.) squid is a http-proxy.
It caches pages, first in RAM, then on the
hard-disk... you're about to put the hard-disk
part on the network, using nfs. Even though
nfs is quite performant it certainly won't beat
the local hdd, specially if the machines on
your network weren't switched.

2.) Assuming that others also have their
homes on the same machine I'd think that
the admin wouldn't be to happy with you
keeping the hdd active for a lot of the time ;)

3.) If you're on a company net, you should
have the admin set-up a proxy for the whole
lot. That makes it way more efficient in terms
of disk & cpu-usage. If the company already
had a proxy going, your effort would be an
utter waste of ressources ;)

Cheers,
Tink