On 1/26/19, Cindy-Sue Causey <butterflyby...@gmail.com> wrote: > On 1/26/19, Pierre Frenkiel <pierre.frenk...@gmail.com> wrote: >> hi, >> I just discovred today that I have every day, in syslog, more than 100000 >> lines of message like: >> >> inetd.service: Got notification message from PID 31376, but reception >> only permitted for main PID 10222 >> >> (I didn't find any useful answer from Google) >> I'm not aware of any not working program, but it's rather frustating, in >> addition that syslog is unusually very big, every day. > > < some rambling of my own snipped > > > So... maybe see if you can identify which two processes go by whatever > numbers appear for the newest lines to see if those packages are still > running. You *possibly* can do that very quickly by placing your > newest numbers where I used "1136" in my example for terminal command > "ps aux | grep 1136": > > $ ps aux | grep 1136 > candyca+ 1136 0.0 0.4 297668 4684 ? Sl Jan24 2:13 > /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray > candyca+ 25753 0.0 0.0 6384 796 pts/1 S+ 15:13 0:00 grep 1136
I had never tracked down what "ps" is. It's a snapshot of running processes. Process snapshot. ps. Found this in "man ps" $ ps -q 1136 -o comm= MUCH NICER. It presents this instead of all that excess feedback from "ps aux": $ ps -q 1136 -o comm= wicd-client MUCH NICER. Much cleaner, much easier to grasp that particular information when needed. < whole bunch more of my own rambling snipped > Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *