# OpenBSD bro.rc unexpected "("

**URL:** <https://community.zeek.org/t/openbsd-bro-rc-unexpected/887>\
**Category:** Zeek\
**Created:** [October 24, 2005, 12:23am UTC](https://community.zeek.org/t/openbsd-bro-rc-unexpected/887 "2005-10-24T00:23:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@Jeff](https://community.zeek.org/u/Jeff)\
**Post date:** [October 24, 2005, 12:23am UTC](https://community.zeek.org/t/openbsd-bro-rc-unexpected/887/1 "2005-10-24T00:23:09Z")

</div>

Hi,

I’ve had the fun of getting Bro installed on OpenBSD and now have a problem with the bro.rc file. Here is the error from the bro.rc:

bash-3.00# /usr/local/bro/etc/bro.rc --start  
/usr/local/bro/etc/bro.rc[476]: syntax error: `(’ unexpected  
bash-3.00#

Here are the corresponding lines form the bro.rc:

468  
469 return ${\_start\_res}  
470 fi  
471  
472 return 0  
473 }  
474  
475  
476 stop() {  
477 # Check to see if bro is running  
478 local \_pid  
479 local \_bro\_is\_running  
480 local \_status\_result  
481  
482 status 2\>/dev/null \>/dev/null  
483 \_status\_result=$?  
484  
485 if [“${\_status\_result}” = ‘0’]; then  
486 # try and stop it

Has anyone else seen this error?

Thanks,

Jeff

When working on the install, we had to copy ip\_ether.h to if\_ether.h and then use the gmake 3.8 to get it to work. I’m running OpenBSD 3.8 from the snapshots. Thanks to all who helped!

---

<div class="post-metadata">

**Author:** ![Roger\_Winslow](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@Roger\_Winslow](https://community.zeek.org/u/Roger_Winslow)\
**Post date:** [October 24, 2005, 3:48pm UTC](https://community.zeek.org/t/openbsd-bro-rc-unexpected/887/2 "2005-10-24T15:48:21Z")

</div>

bro.rc does it's best at catching failures to start but unfortunately  
doesn't catch it 100% of the time. Sometimes programs that segfault can  
produce error that you are seeing. It is likely that what is happening  
is that Bro is unable to start for some reason and the shell script is  
failing to catch the error. Is there anything in the \*.info file in your  
$BROLOGS directory after this happens? If so could you send me that?  
Another thing to try is by starting Bro manually from the command line.  
I suspect if you do this you will get closer to what the real problem is.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Roger Winslow

Jeff wrote:

---

<div class="post-metadata">

**Author:** ![Camiel\_Dobbelaar](https://avatars.discourse-cdn.com/v4/letter/c/9d8465/32.png) [@Camiel\_Dobbelaar](https://community.zeek.org/u/Camiel_Dobbelaar)\
**Post date:** [November 10, 2005, 8:02pm UTC](https://community.zeek.org/t/openbsd-bro-rc-unexpected/887/3 "2005-11-10T20:02:01Z")

</div>

"stop" is an alias that is defined automatically in OpenBSD sh (pdksh):

camield@zigzag $ alias stop  
stop='kill -STOP'

I made some other adjustments to bro.rc as well, diff at the bottom.

---

<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:37pm UTC](https://community.zeek.org/t/openbsd-bro-rc-unexpected/887/4 "2022-05-06T15:37:43Z")

</div>


