Bug #4193
closedlibevent-2.0.so.5 symlink missing on 2.2 RC
0%
Description
on 2.2 beta I have ldd /usr/local/sbin/check_reload_status with all libs ok
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800a4f000)
        libc.so.7 => /lib/libc.so.7 (0x800c91000)
        libthr.so.3 => /lib/libthr.so.3 (0x801023000)
But on 2.2 RC built on Thu Jan 08 03:14:18 CST 2015, ldd returns 
/usr/local/sbin/check_reload_status:
        libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
        libevent-2.0.so.5 => not found (0)
        libc.so.7 => /lib/libc.so.7 (0x800a4f000)
a symlink just like it was used on 2.2 BETA fix the issue and check_reload_status get working and also all pf rules that packages like squid(for transparent proxy) creates
related forum post:
https://forum.pfsense.org/index.php?topic=84638.msg474145#msg474145
      
      Updated by Jim Thompson almost 11 years ago
      
    
    - Assignee set to Chris Buechler
 
Not seeing it.
[2.2-RC][admin@<Yeah, no>]/root: cat /etc/version*
2.2-RC
Thu Jan 08 19:13:15 CST 2015
d97dd424371014e766f63cbbffa0e92e0748f38e
[2.2-RC][admin@<Yeah, no>]/root: ldd /usr/local/sbin/check_reload_status
/usr/local/sbin/check_reload_status:
    libsbuf.so.6 => /lib/libsbuf.so.6 (0x80084c000)
    libevent-2.0.so.5 => /usr/local/lib/libevent-2.0.so.5 (0x800a4f000)
    libc.so.7 => /lib/libc.so.7 (0x800c91000)
    libthr.so.3 => /lib/libthr.so.3 (0x801023000)
Might be related to the hung builder earlier today.
      
      Updated by Chris Buechler almost 11 years ago
      
    
    - Project changed from pfSense Packages to pfSense
 - Status changed from New to Rejected
 
it's there on 2.2-RC both 32 and 64 bit, nano and full. It's not a symlink and never has been. I double checked the obsoleted files list to make sure we weren't removing it and that's fine also. Given only 2 people have seen it that I can find, and both are messing with the squid3 files Marcello put out in the linked thread, seems it's something to do with that which blows away that file somehow.