Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ip_vs_ftp\s+causing\s+ip

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ip_vs_ftp\s+causing\s+ip_vs\s+oops\s+on\s+module\s+load\.\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: ip_vs_ftp causing ip_vs oops on module load. (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Thu, 19 May 2011 23:13:44 +0300 (EEST); Hello, Yes, it is possible, if we find solution to trigger register_ip_vs_app_inc() calls with such controls... May be app have to export some method(s) for this to work. OK, then let's use this solu; /html/lvs-devel/2011-05/msg00033.html (14,621 bytes)
2. Re: ip_vs_ftp causing ip_vs oops on module load. (score: 1): Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>; Date: Thu, 19 May 2011 12:19:21 +0200; If we talk about the long term solution, applications that affects other netns should have their own data. ex. like the ftp, ports should be per netns ipvsadm --appftp [port list] Doesn't matter, jus; /html/lvs-devel/2011-05/msg00030.html (15,324 bytes)

Current List: 1 - 2
Page: [1]