This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[SOLVED] cupsd cannot write to /var/log/cups

Tags: None
(comma "," separated)
User avatar
google01103
Manager
Posts
6668
Karma
25
maybe ask if it's normal on the Kubunt forum as it is a distro specific question


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
sparhawk
Registered Member
Posts
433
Karma
0
OS
google01103 wrote:maybe ask if it's normal on the Kubunt forum as it is a distro specific question

Good idea. Did you mean the Kubuntu forum on this website? I guess that's "Linux"? Or did you mean an external site?
User avatar
google01103
Manager
Posts
6668
Karma
25
you could do eitherm but distro specific issues are best addressed on their site, of course the question then is the Ubuntu or Kubuntu forum, as this is not KDE related either should work


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
sparhawk
Registered Member
Posts
433
Karma
0
OS
Thanks, I've posted a question at kubuntuforums.
User avatar
sparhawk
Registered Member
Posts
433
Karma
0
OS
Also, as for this issue:
sparhawk wrote:I did have an additional job previously, that must've been wiped when I did the purge/install. I added that back, and now anacron starts up fine (without stopping). I'm not sure why that's considered a job and the others are not, but it's all working fine now, thanks...

I just checked the boot.log again, and it's again saying "stopping" despite being okay for a cycle or so. Well, I won't worry too much about it, but I'll keep an eye on my anacron jobs to make sure that they're running okay. AFAIK it's a bit difficult to tell if anacron is running or not, unless I make a job and follow it.
User avatar
sparhawk
Registered Member
Posts
433
Karma
0
OS
Just to add some closure to this thread, I found a backup from two months ago (before I did the clean install of Kubuntu), and it also has numerous empty "Starting" messages in /etc/log/boot.log. So I won't worry about that.

OTOH, it did not have the message about stopping anacron, which I still have in my current boot.log. However, I checked in my syslog, and it appears that my anacron job ran fine today, so all is well.

Thank you very much to everyone for their help!!


Bookmarks



Who is online

Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, Sogou [Bot]