Search Results

Search found 2 results on 1 pages for 'dsadinoff'.

Page 1/1 | 1 

• Where do yum-updatesd dbus messages go on Centos-5.7?

  - by dsadinoff

  I'm unfamiliar with dbus and friends. Centos 5.7 seems to ship with yum-updatesd sending messages to dbus. I have a feeling I should just change that to email and be done with it, but I'd like to understand why it's configured that way. Where do the messages go from dbus? Is something subscribed? Are they queueing inside dbus somehow? How could I figure this out on my own? /etc/dbus-1/system.d/yum-updatesd.conf seems to configure dbus to allow for traffic from root on the edu.duke.linux.yum interface, if that helps.

  Read the article

• Should tripwire be entering /proc?

  - by dsadinoff

  When initializing the db with tripwire --init it spat out a bunch of errors pertaining to /proc: ### Warning: File system error. ### Filename: /proc/16982/fd/4 ### No such file or directory ### Continuing... ### Warning: File system error. ### Filename: /proc/16982/fdinfo/4 ### No such file or directory ### Continuing... ### Warning: File system error. ### Filename: /proc/16982/task/16982/fd/4 ### No such file or directory ### Continuing... ### Warning: File system error. ### Filename: /proc/16982/task/16982/fdinfo/4 ### No such file or directory ### Continuing... ### Warning: Duplicate object encountered. ### /proc/sys/net/ipv6/neigh This feels like noise. The twpol.txt file has the following clause: # # Critical devices # ( rulename = "Devices & Kernel information", severity = $(SIG_HI), ) { /dev -> $(Device) ; /proc -> $(Device) ; } Which, if I understand it right, is going to cause tripwire to care deeply about the entire contents of /proc. Shouldn't it just care about the static parts of /proc like the drivers and such, and not the per-pid stuff? Why does it ship like this?

  Read the article

1