How can I stop an amok running process from logging to systemd?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
There's a process on my system called demond which logs around 100 entries to the systemd journal every 15 seconds:
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev0. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev1. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev2. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev3. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev4. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev5. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev6. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev7. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev8. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev9. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev10. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev11. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev12. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev13. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev14. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev15. No such file or directory
This fills up the journal very quickly and creates permanent disk access, which drains battery. The entries all have priority 7 (debug).
demond is part of the Lexmark printer driver. I guess they use it for Wifi discovery of devices. I contacted Lexmark support and they said they cannot change the driver, and there's no way to suppress those messages. And since the driver is closed source, I cannot change it myself.
I know that I can suppress debug level 7 altogether using MaxLevelStore=info in journald.conf, but this suppresses the debug level for all processes.
Is there a way to suppress logging for a certain process such as demond?
I'm using ArchLinux with latest systemd 208. I don't use syslog-ng or rsyslog.
logs systemd
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
add a comment |
There's a process on my system called demond which logs around 100 entries to the systemd journal every 15 seconds:
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev0. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev1. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev2. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev3. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev4. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev5. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev6. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev7. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev8. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev9. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev10. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev11. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev12. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev13. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev14. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev15. No such file or directory
This fills up the journal very quickly and creates permanent disk access, which drains battery. The entries all have priority 7 (debug).
demond is part of the Lexmark printer driver. I guess they use it for Wifi discovery of devices. I contacted Lexmark support and they said they cannot change the driver, and there's no way to suppress those messages. And since the driver is closed source, I cannot change it myself.
I know that I can suppress debug level 7 altogether using MaxLevelStore=info in journald.conf, but this suppresses the debug level for all processes.
Is there a way to suppress logging for a certain process such as demond?
I'm using ArchLinux with latest systemd 208. I don't use syslog-ng or rsyslog.
logs systemd
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
add a comment |
There's a process on my system called demond which logs around 100 entries to the systemd journal every 15 seconds:
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev0. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev1. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev2. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev3. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev4. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev5. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev6. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev7. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev8. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev9. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev10. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev11. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev12. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev13. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev14. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev15. No such file or directory
This fills up the journal very quickly and creates permanent disk access, which drains battery. The entries all have priority 7 (debug).
demond is part of the Lexmark printer driver. I guess they use it for Wifi discovery of devices. I contacted Lexmark support and they said they cannot change the driver, and there's no way to suppress those messages. And since the driver is closed source, I cannot change it myself.
I know that I can suppress debug level 7 altogether using MaxLevelStore=info in journald.conf, but this suppresses the debug level for all processes.
Is there a way to suppress logging for a certain process such as demond?
I'm using ArchLinux with latest systemd 208. I don't use syslog-ng or rsyslog.
logs systemd
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
There's a process on my system called demond which logs around 100 entries to the systemd journal every 15 seconds:
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev0. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev1. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev2. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev3. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev4. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev5. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev6. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev7. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev8. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev9. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev10. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev11. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev12. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev13. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev14. No such file or directory
Okt 11 04:58:42 scarecrow demond[1692]: [P:1692 T:108160832] src/discovery.c : 158 getHidDevices -- failed in opening HIDDEV file: /dev/hiddev15. No such file or directory
This fills up the journal very quickly and creates permanent disk access, which drains battery. The entries all have priority 7 (debug).
demond is part of the Lexmark printer driver. I guess they use it for Wifi discovery of devices. I contacted Lexmark support and they said they cannot change the driver, and there's no way to suppress those messages. And since the driver is closed source, I cannot change it myself.
I know that I can suppress debug level 7 altogether using MaxLevelStore=info in journald.conf, but this suppresses the debug level for all processes.
Is there a way to suppress logging for a certain process such as demond?
I'm using ArchLinux with latest systemd 208. I don't use syslog-ng or rsyslog.
logs systemd
logs systemd
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
edited Oct 14 '13 at 10:26
dmoebius
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
asked Oct 14 '13 at 9:32
dmoebiusdmoebius
1665
1665
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Turned out there's an environment variable called ENABLE_D_LOG=0|1 which is 1 by default and which is responsible for the logging madness. Setting it to 0 shuts up the driver. So I created a wrapper script for demond that sets ENABLE_D_LOG=0 and then calls the original demond:
# cd /usr/local/lexmark/legacy/bin
# mv demond demond.orig
# cat > demond <<EOF
#!/bin/sh
export ENABLE_D_LOG=0
/usr/local/lexmark/legacy/bin/demond.orig $@
EOF
# chmod +x demond
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f95971%2fhow-can-i-stop-an-amok-running-process-from-logging-to-systemd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Turned out there's an environment variable called ENABLE_D_LOG=0|1 which is 1 by default and which is responsible for the logging madness. Setting it to 0 shuts up the driver. So I created a wrapper script for demond that sets ENABLE_D_LOG=0 and then calls the original demond:
# cd /usr/local/lexmark/legacy/bin
# mv demond demond.orig
# cat > demond <<EOF
#!/bin/sh
export ENABLE_D_LOG=0
/usr/local/lexmark/legacy/bin/demond.orig $@
EOF
# chmod +x demond
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
add a comment |
Turned out there's an environment variable called ENABLE_D_LOG=0|1 which is 1 by default and which is responsible for the logging madness. Setting it to 0 shuts up the driver. So I created a wrapper script for demond that sets ENABLE_D_LOG=0 and then calls the original demond:
# cd /usr/local/lexmark/legacy/bin
# mv demond demond.orig
# cat > demond <<EOF
#!/bin/sh
export ENABLE_D_LOG=0
/usr/local/lexmark/legacy/bin/demond.orig $@
EOF
# chmod +x demond
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
add a comment |
Turned out there's an environment variable called ENABLE_D_LOG=0|1 which is 1 by default and which is responsible for the logging madness. Setting it to 0 shuts up the driver. So I created a wrapper script for demond that sets ENABLE_D_LOG=0 and then calls the original demond:
# cd /usr/local/lexmark/legacy/bin
# mv demond demond.orig
# cat > demond <<EOF
#!/bin/sh
export ENABLE_D_LOG=0
/usr/local/lexmark/legacy/bin/demond.orig $@
EOF
# chmod +x demond
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
Turned out there's an environment variable called ENABLE_D_LOG=0|1 which is 1 by default and which is responsible for the logging madness. Setting it to 0 shuts up the driver. So I created a wrapper script for demond that sets ENABLE_D_LOG=0 and then calls the original demond:
# cd /usr/local/lexmark/legacy/bin
# mv demond demond.orig
# cat > demond <<EOF
#!/bin/sh
export ENABLE_D_LOG=0
/usr/local/lexmark/legacy/bin/demond.orig $@
EOF
# chmod +x demond
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
edited 1 hour ago
Rui F Ribeiro
41.9k1483142
41.9k1483142
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
answered Oct 14 '13 at 10:35
dmoebiusdmoebius
1665
1665
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f95971%2fhow-can-i-stop-an-amok-running-process-from-logging-to-systemd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
