search for: acrtiv

...like to do a client server version of R where the server can run on a unix box and the client is excel ond a win machine. the easiest solution would be running a stdin-stdout version of the server through inetd. but this is vulnerable. so what is needed is a sandbox version of the server, where no acrtive access to the file system is open and where spawning processes is disabled. are there any plans for doing such a version? -- Erich Neuwirth, Computer Supported Didactics Working Group Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-38624 Fax: +43-1-4277-9386 -.-.-.-.-.-.-.-.-....

I have 2 firewall in HA with keepalived. Can I use active the same tinc configuration on 2 firewalls ? using tun Interface with same ip on all 2 nodes is a problem ? tun device advertise itself on the network having an IP/MAC pairs (ARP) or the IP is only used by the system internally for routing so using the same configuration is right ? so one firewall be active, the other is passive. With this

...e WAN connection so all of that work well with such little connection interruption. The problem is that to avoid to tie together Keepalived and Tinc, ie: put in Keepalived primary-backup.sh state change script commands to stop Tinc on Passive node and to start on active node, we try to leave Tinc acrtive always on all firewalls (also those are passive for keepalived - no VIP active) and use the VIP as Tinc tun virtual interface. Naturally when one node is active it has the Keepalived managed VIP active and Tinc Virtual Interface using tun has as IP the same as Keepalived VIP with different netmask...

...nnection so all of that work well with such little connection interruption. > > The problem is that to avoid to tie together Keepalived and Tinc, ie: put in Keepalived primary-backup.sh state change script commands to stop Tinc on Passive node and to start on active node, we try to leave Tinc acrtive always on all firewalls (also those are passive for keepalived - no VIP active) and use the VIP as Tinc tun virtual interface. > Naturally when one node is active it has the Keepalived managed VIP active and Tinc Virtual Interface using tun has as IP the same as Keepalived VIP with different ne...

...ection so all of that work well with such little connection interruption. > > The problem is that to avoid to tie together Keepalived and Tinc, ie: put in Keepalived primary-backup.sh state change script commands to stop Tinc on Passive node and to start on active node, we try to leave Tinc acrtive always on all firewalls (also those are passive for keepalived - no VIP active) and use the VIP as Tinc tun virtual interface. > Naturally when one node is active it has the Keepalived managed VIP active and Tinc Virtual Interface using tun has as IP the same as Keepalived VIP with different n...