C Compiler requirement
Phil.Cryer at edwardjones.com
Mon Nov 5 21:07:24 CET 2007
If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments. If you no longer wish to receive e-mail from Edward Jones, please send this request to messages at edwardjones.com. You must include the e-mail address that you wish not to receive e-mail communications. For important additional information related to this e-mail, visit www.edwardjones.com/US_email_disclosure
From: varnish-misc-bounces at projects.linpro.no
[mailto:varnish-misc-bounces at projects.linpro.no] On Behalf Of Cryer,Phil
Sent: Monday, November 05, 2007 1:44 PM
To: varnish-misc at projects.linpro.no
Subject: RE: C Compiler requirement
>>Is there any way Varnish can compile that beforehand, and then have
>>that Shared Object used on the next launch instead of having it
> It's not inherently impossible, but does raise som concerns about
version skew between
> the compiled VCL and the varnishd binary.
> It shouldn't be too much work to implement I think.
Replying to myself:
|| So where is the shared object that Varnish creates on startup?
bash-3.00# ls -l /var/lib/varnish/`hostname`
-rwxr-xr-x 1 root root 19800 Nov 5 14:03 bin.XXpiVDV1
-rw------- 1 root root 22836 Nov 5 14:03 _.c
-rw-r--r-- 1 root root 8389176 Nov 5 14:03 _.vsl
bash-3.00# file *
bin.XXpiVDV1: ELF 64-bit LSB shared object, AMD x86-64, version 1
(SYSV), not stripped
_.c: ASCII C program text
So I know where the current shared obj is, now I just need to figure out
(or have implemented):
||[...] is there a DAEMON_OPTS variable I can set to make Varnish use an
||object instead of regen'ing a new one on startup? I suspect that last
one would be the only
||functionality missing currently.
More information about the varnish-misc