2 added 27 characters in body
source | link

My system keeps getting wedged because an scdaemon process has been spawned that has grown to consume all free memory on the computer. (I do not use, and have never used, smart cards in the vicinity of this system, so scdaemon shouldn't be running at all.)

I could implement something like a cronjob that runs pkill scdaemon every five seconds, but I'd rather find and destroy the root issue that's causing this behavior.

What files can I check and what tools can I use to track down why this daemon keeps getting started? I've done a pstree and the most I've been able to determine is that they're getting started by gpg-agent, which hasn't helped. I haven't found any log that's been able to shed some light on this.

My system keeps getting wedged because an scdaemon process has been spawned that has grown to consume all free memory on the computer. (I do not use, and have never used, smart cards in the vicinity of this system, so scdaemon shouldn't be running at all.)

I could implement something like a cronjob that runs pkill scdaemon every five seconds, but I'd rather find and destroy the root issue that's causing this behavior.

What tools can I use to track down why this daemon keeps getting started? I've done a pstree and the most I've been able to determine is that they're getting started by gpg-agent, which hasn't helped. I haven't found any log that's been able to shed some light on this.

My system keeps getting wedged because an scdaemon process has been spawned that has grown to consume all free memory on the computer. (I do not use, and have never used, smart cards in the vicinity of this system, so scdaemon shouldn't be running at all.)

I could implement something like a cronjob that runs pkill scdaemon every five seconds, but I'd rather find and destroy the root issue that's causing this behavior.

What files can I check and what tools can I use to track down why this daemon keeps getting started? I've done a pstree and the most I've been able to determine is that they're getting started by gpg-agent, which hasn't helped. I haven't found any log that's been able to shed some light on this.

1
source | link

Why is scdaemon ballooning out of control?

My system keeps getting wedged because an scdaemon process has been spawned that has grown to consume all free memory on the computer. (I do not use, and have never used, smart cards in the vicinity of this system, so scdaemon shouldn't be running at all.)

I could implement something like a cronjob that runs pkill scdaemon every five seconds, but I'd rather find and destroy the root issue that's causing this behavior.

What tools can I use to track down why this daemon keeps getting started? I've done a pstree and the most I've been able to determine is that they're getting started by gpg-agent, which hasn't helped. I haven't found any log that's been able to shed some light on this.