[Bro-Dev] [JIRA] (BIT-1067) topic/jsiwek/extract-limit

2013-08-23 Thread Robin Sommer (JIRA)

 [ 
https://bro-tracker.atlassian.net/browse/BIT-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robin Sommer updated BIT-1067:
--

Status: Closed  (was: Merge Request)

 topic/jsiwek/extract-limit
 --

 Key: BIT-1067
 URL: https://bro-tracker.atlassian.net/browse/BIT-1067
 Project: Bro Issue Tracker
  Issue Type: Improvement
  Components: Bro
Affects Versions: git/master
Reporter: Jon Siwek
Assignee: Robin Sommer
 Fix For: 2.2


 Two changes in this branch:
 - Add ability to limit size of extracted files.
 - Refactor file analyzer plugins to create classes via macros.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://bro-tracker.atlassian.net/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


[Bro-Dev] [JIRA] (BIT-1068) cpu_pin problem

2013-08-23 Thread Daniel Thayer (JIRA)

[ 
https://bro-tracker.atlassian.net/browse/BIT-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13715#comment-13715
 ] 

Daniel Thayer commented on BIT-1068:


Which OS are you using?  What does your node.cfg look like?


 cpu_pin problem
 ---

 Key: BIT-1068
 URL: https://bro-tracker.atlassian.net/browse/BIT-1068
 Project: Bro Issue Tracker
  Issue Type: Problem
  Components: BroControl
Affects Versions: 2.2
Reporter: Seth Hall
Assignee: Daniel Thayer

 I seem to be having a problem with the cpu_pin feature of broctl.  I'm 
 getting the following output...
 [rootsh@xx worker-1-6]# cat stderr.log 
 sched_setaffinity: Invalid argument
 failed to set pid 0's affinity.
 Daniel, any clue what I should be looking into or information I can provide?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://bro-tracker.atlassian.net/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev


[Bro-Dev] [JIRA] (BIT-1068) cpu_pin problem

2013-08-23 Thread Seth Hall (JIRA)

[ 
https://bro-tracker.atlassian.net/browse/BIT-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716#comment-13716
 ] 

Seth Hall commented on BIT-1068:


I feel so ashamed. :)

I entered '8' as a cpu because it was an 8 core cpu.  Unfortunately I was off 
by one since the last cpu core is addressed at '7'.  Sigh.

Do you think that's something you could catch and detect?  A better error 
message would be super helpful. :)

 cpu_pin problem
 ---

 Key: BIT-1068
 URL: https://bro-tracker.atlassian.net/browse/BIT-1068
 Project: Bro Issue Tracker
  Issue Type: Problem
  Components: BroControl
Affects Versions: 2.2
Reporter: Seth Hall
Assignee: Daniel Thayer

 I seem to be having a problem with the cpu_pin feature of broctl.  I'm 
 getting the following output...
 [rootsh@xx worker-1-6]# cat stderr.log 
 sched_setaffinity: Invalid argument
 failed to set pid 0's affinity.
 Daniel, any clue what I should be looking into or information I can provide?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://bro-tracker.atlassian.net/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev