Ok, maybe I found a very ugly workaround!! I looking at the source code of ikec where are many functions related to user input, but I don't need user input at all because all needed data are passed as cmd line arguments with '-a' option, so I commented all Editline related stuff and leave all related functions empty...last but not least the while loop in main.cpp now is only a sleep(30) function.
Now ikec stop wasting cpu and early test is going fine...I hope some shrew soft guys can confirm this is a reasonable workaround and maybe improve it or point me to a better solution On Tue, Mar 13, 2012 at 10:43 AM, lestoilfante <[email protected]>wrote: > Hello, > I'm currently doing some test with SS version 2.2.0-beta-2 on linux kernel > 2.6.32. SS is compiled with -DQTGUI=NO option, so I want to control > connection process from shell. If I start connection from interactive shell > with "ikec -r $vpnconf_file -u $vpn_user -p $vpn_pass -a" everything is ok > and ikec is blocking my shell expecting user input, anyway I want to > control vpn connection from cron script so I put "( ( ikec -r $vpnconf_file > -u $vpn_user -p $vpn_pass -a & ) & )" inside a shell script started from > cron, in this case vpn is bringed up but ikec cpu usage grow up to 70-80%. > Do you have any suggestions on how can I avoid this? > > Thank you >
_______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
