The computer finally stopped screaming at me. I still want to know what was wrong. I am not interested in turning off or attenuating the bell.
Thinking more clearly this morning, it occurred to me to sort all the files and folders in /var/log by time stamp. Then I found the folder 'upstart' which was last modified last night at about the time of the bleeps. Opening the folder I found systemd-logind.log.gz*, which contained the file systemd-logind.log.2, which contained only the following: Removed session c14. New session c15 of user nobody. Removed session c15. New session c16 of user nobody. Removed session c16. New session c17 of user nobody. *[Rant] Why was it necessary to gzip this file? I had to open file-roller as root in order to get at the text. Bah. For the record, there is only one user account on this computer, that is me, and I sure didn't name myself 'nobody.' I have been continuously logged in as jjj without problem since I returned from the Clinic last Sunday, yet the bleeps only started just last night. Google tells me that user 'nobody' is used to run daemons and programs that do not require privileges, as a security measure. Also, apparently 'nobody' can send messages to other users. I take that to mean that last night 'nobody' wanted to tell jjj something, and thus made the computer bleep at him. OK, fine. So listen, 'nobody': If you want to tell me something you're going to have to be more specific than "bleep." Give me a clue, 'k? So I still don't know what caused the bleeps, and I still want to figure it out. If something is wrong, common sense tells me that I should fix it, not ignore it or cover it up by turning off the bell. Any suggestions? _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
