The user that failed starting seccomp just had the wrong order.cpu, it works for him now. And here nice update for one more popular distro shipping with seccomp enabled: https://www.cpushare.com/blog/CPUShare/article/84/ > The Ubuntu failure at runtime is certainly something minor and > probably not their fault (thought I doubt it's my fault). I need to > help them debug this. It might be a glibc issue. We'll see. Now I really need to sort out this Ubuntu issue, a very close friend of mine living in my city just kindly sent me strace debug data about that... now I'm really curious to find what the Ubuntu problem is! ;) -- cpushare-discuss_X_at_X_cpushare.com mailing list - http://www.cpushare.com/ To unsubscribe, send mail to cpushare-discuss-unsubscribe_X_at_X_cpushare.comReceived on 2007-09-20 01:49:20
Click here to return to to homepage.
Disclaimer: the messages posted here are under the sole responsibility of the poster: cpushare.com is publishing mailing list messages in real time while storing safely all the logs containing the relevant IP addresses, timings and mail hops. If you find anything not appropriate in these messages please send a notification through this form. Thank You.
CPUShare Discuss has been converted to html using hypermail 2.2.0.