Arek B.'s questions

When varnish cache is empty and I got X client requests for the same asset - Varnish gathers the clients and issues 1 backend fetch.

Do you know if there's possibility to control how many requests are held until fetch (or time window size)? - I would like to have backend fetch more frequently so the clients would wait shorter time.

When I test with return(pass) - I got nice flow, no long times for the client, but I got no caching - and because caching is set by backend - I would like to stay with "return(lookup)" which enables antidogpile effect - good but sometimes bad (because of holding reqs...)

EDIT: Kind of solution in my comments :)

I have four nodes A-D with service1 clone (clone-max 3) and with 3 virtual IPs. I have constraints - clone-ip1, clone-ip2, clone-ip3 - this works well when only pacemaker handles services.

I'd like Pacemaker to "audit" the nodes automaticly so when service is started without constraint pacemaker stops it. It seems that when nodes A, B, C works in active state - pacemaker doesn't care what is going on on node D. When I force reprobe by crm_resource -P - it stops unnecessary service on node D. Is there a way to make pacemaker check all nodes? (multiple_active doesn't seem to work...)

I want nginx to serve as a ssl proxy but for host: "ssl.example.com"

at the same time I want nginx to serve "nginx is ok" website for host: "ssl-check.example.com" (this is just example, please don't suggest any monitoring tools here)

for other hosts pointing to my IP I want to serve 404 or whatever.
- I don't care for certificate mismatch - so SNI is not what I want here.
- I don't want to use described as pitfall solution and use something like

if ($host != $server_name) {
root /var/www/errors/404

All these on single IP.

I have working ssl

server {

with server_name ssl.example.com - working as I want.

another ssl

server {

with server_name ssl_check.example.com - showing "nginx is ok"

and last server (also ssl) without server_name (or with "_" as name) which is supposed to serve 404 but it doesn't work...

SOLVED
My config using the solution looks now (and works) like:

1. server with "listen 443 ssl;" serving proxy
2. server with "listen 443 ssl;" serving "nginx is ok"
3. server with "listen 443 ssl default_server;" and with "location / return 404"

If this config can be in any way dangerous - don't hesitate to put me to shame. Thans

I have users in external database. So far - ssh, postfix, dovecot and some others - use entries with no problem.
I have Maildirs inside /home/[user] and if the homedir exists - everything is ok - sending, receiving.
If homedir does not exist Postfix/Dovecot prints error, ssh - after login results in brand new homedir made - it uses pam_mkhomedir.so entry in /etc/pam.d/[in few files].

Postfix/Dovecot - successfully use pam.d with database backend but ignores entries with pam_mkhomedir - I have read a lot of hints in which file and on what position place it.
Maybe it's a matter of nameing file /etc/pam.d/[file] ??

I've got some iSCSI/FC storage, currently using only iSCSI. I have in general no problems with mounting LUNs - under Linux and under Windows.

Unfortunately - when I add LUN for my Linux iSCSI initiator - I receive info in messages:

Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments

and new LUN does not appear in

fdisk -l

If I restart iscsi daemon - I get new LUN but loose connection with mounted old LUNs, moreover - devices letters (dev/sd..) are changing.

On Windows - new LUN is visible at once and can be mounted with no affecting previous ones.

Is there special option in

iscsiadm

(I tried such as "rescan" but with no success)?

I have multiple servers in WEB cluster (identical configuration for all of them, despite the IP)

How do you deploy changes in configs on multile servers?

I make the new config, then create config per every server (placing correct IP), and next:

• upload them on every server, replacing old ones (rsync over ssh)
• set on every server a job which reloads webserver at the same time (servers use ntp). - this done by issuing commands by script (to save time for logging in)
• before adding a job for server reload - there's checksum test of the config on the server) - an a notification in case of fail

How do you see such method? What should be the "professional way :) ? (I don't say my way doesn't work... it works and saves my time not used for logging on every webserver.)

Regards,