# Removal of multiple input sources?

**URL:** <https://community.zeek.org/t/removal-of-multiple-input-sources/5805>\
**Category:** Zeek\
**Created:** [August 14, 2019, 6:23pm UTC](https://community.zeek.org/t/removal-of-multiple-input-sources/5805 "2019-08-14T18:23:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Wojtulewicz](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/tim_wojtulewicz/32/594_2.png) [@Tim\_Wojtulewicz](https://community.zeek.org/u/Tim_Wojtulewicz)\
**Post date:** [August 14, 2019, 6:23pm UTC](https://community.zeek.org/t/removal-of-multiple-input-sources/5805/1 "2019-08-14T18:23:08Z")

</div>

We’re currently considering a rewrite of the existing main IO loop in Zeek (see [https://github.com/zeek/zeek/issues/264](https://github.com/zeek/zeek/issues/264) for more detail). As part of this work, we’re planning to remove the ability for a single Zeek process to handle multiple input sources (either interface or pcap) simultaneously, since it would simplify the code somewhat. The case of multiple interfaces is already handled by running multiple workers. Is anyone actively using the multiple pcap functionality that would be broken by this change?

Tim @ Corelight

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:46pm UTC](https://community.zeek.org/t/removal-of-multiple-input-sources/5805/2 "2022-05-06T15:46:42Z")

</div>