Re: wtmpx file incrases fast because of squid in inittab

Start squid with -N. Squid 1.x used to stay in the foreground, and
running it from inittab was easy. Now squid 2.x forks into the
background by default, causing init to think it's terminated. 'squid -N'
prevents that.

D

Sherif Diaa El-Din - Email wrote:
>
> Hi All,
>
> I am using squid2.2STABE4 on sun solaris 2.6
> I configured squid to run automatically when the system starts from
> inittab as in faq
>
> sq:3:respawn:/usr/local/squid/bin/squid.sh < /dev/null >> /tmp/squid.log
> 2>&1
>
> and squid.sh is :
> #!/bin/sh
> C=/usr/local/squid
> PATH=/usr/bin:$C/bin
> TZ=PST8PDT
> export PATH TZ
>
> notify="root"
> cd $C
> umask 022
> sleep 10
> while [ -f /tmp/nosquid ]; do
> sleep 1
> done
> /usr/bin/tail -20 $C/logs/cache.log \
> | Mail -s "Squid restart on `hostname` at `date`" $notify
> exec bin/squid -CYs
>
> the problem is that I found /var/wtmpx increases so fast that /var gets
> filled, when I checked it I found squid.sh is written in it few times per
> second
>
> so I figured out that squid.sh dies, I didn't find a file
> called /tmp/nosquid, I guess that is why inittab starts it again
> so why isn't /tmp/nosquid is created , and which process should start it?
> and how can I overcome this problem ?
>
> PS: I recently have installed patches for year 2000 from sun, while the
> squid was running, also IPFilter package is installed, I didn't find
> problems in /var before installing this patches, does it have anything to
> do with the /tmp/nosquid ?
>
> Best Regards
> Sherif Mohamad
> System Administrator
Received on Fri Sep 24 1999 - 22:07:58 MDT