[opensuse] huge number of gs_* files in /tmp
Last week I tried creating a postscript file from a .PNG file that I had open with Gwenview. For some reason it didn't work out, it hung and dragged the machine down and I couldn't kill it and had to reboot. Since then, as I reboot the machine each morning, I find that after a few minutes /tmp fills us with a few THOUSAND GS_* files. Most are empty, a few are a round 10K or so. This paralyses other activities. They are owned by 'anton' -- of course. I can't figure out what is causing this. I've delayed starting KDE, and that delays the creation and I've checks, so it isn't a CRON job. I've gone in via systemsettings and I can't see a startup job that would account for this; I only have a dropbox start and a video setting. I run a 'ps' and I can't see what might be responsible. Any suggestions as to where I should look to see what's responsible for this? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 12:15 PM, Anton Aylward wrote:
Last week I tried creating a postscript file from a .PNG file that I had open with Gwenview.
For some reason it didn't work out, it hung and dragged the machine down and I couldn't kill it and had to reboot.
Since then, as I reboot the machine each morning, I find that after a few minutes /tmp fills us with a few THOUSAND GS_* files. Most are empty, a few are a round 10K or so. This paralyses other activities. They are owned by 'anton' -- of course.
I can't figure out what is causing this. I've delayed starting KDE, and that delays the creation and I've checks, so it isn't a CRON job.
I've gone in via systemsettings and I can't see a startup job that would account for this; I only have a dropbox start and a video setting.
I run a 'ps' and I can't see what might be responsible.
Any suggestions as to where I should look to see what's responsible for this?
Maybe you can catch the process(es) red-handed lsof | grep -F '/tmp/gs_' ? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 07:42 AM, Bernhard Voelker wrote:
Maybe you can catch the process(es) red-handed
lsof | grep -F '/tmp/gs_'
I will try to be more vigilant tomorrow :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 07:42 AM, Bernhard Voelker wrote:
Maybe you can catch the process(es) red-handed
lsof | grep -F '/tmp/gs_'
Well, it was a nice idea, but it all went by too fast and by the time I got to run this the files were there and whatever created them was long gone. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-15 16:00, Anton Aylward wrote:
On 11/15/2016 07:42 AM, Bernhard Voelker wrote:
Maybe you can catch the process(es) red-handed
lsof | grep -F '/tmp/gs_'
Well, it was a nice idea, but it all went by too fast and by the time I got to run this the files were there and whatever created them was long gone.
Script it. Run several times in a loop, pipe to a file. Hook on /etc/init.d/before.local and/or /etc/init.d/after.local -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/15/2016 12:46 PM, Carlos E. R. wrote:
On 2016-11-15 16:00, Anton Aylward wrote:
On 11/15/2016 07:42 AM, Bernhard Voelker wrote:
Maybe you can catch the process(es) red-handed
lsof | grep -F '/tmp/gs_'
Well, it was a nice idea, but it all went by too fast and by the time I got to run this the files were there and whatever created them was long gone.
Script it. Run several times in a loop, pipe to a file. Hook on /etc/init.d/before.local and/or /etc/init.d/after.local
And I do mean !FAST! I rebooted and hot keyed to alt-F1, logged in as toot and ran that 'lsof' in a loop to a file, accumulating. Then I hotkeyed back to the GUI screen, logged in, let KDE start up. Sure enough, 528 files were created filling up /tmp. However all that was captured is this: gs 2401 anton 4u REG 254,9 10760625 41 /tmp/gs_P718lh gs 2401 anton 5u REG 254,9 6128 49 /tmp/gs_50oT46 So yes, it was a postscript "ghostscript" process, which doesn't tell me anything I didn't already know. As I said, this was an artefact of an aborted attempt to print a postscript file from within Gwenview. But it still doesn't tell me how this came about. It's within KDE and within the start-up, but I can't find anything in the .kde4 tree that relates to it. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 04:02 PM, Anton Aylward wrote:
It's within KDE and within the start-up, but I can't find anything in the .kde4 tree that relates to it.
Can't remember if this was covered before or not.... It might be kde trying to restore a prior session. In KDE configure desktop Under the System Administration group select Startup and shutdown Then Session management. Then in the on login section check the start with empty session. Then log out. Maybe reboot, IDK. somehow empty /tmp Then log in. Then remember to change this setting to what ever you had before. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 07:27 PM, John Andersen wrote:
On 11/15/2016 04:02 PM, Anton Aylward wrote:
It's within KDE and within the start-up, but I can't find anything in the .kde4 tree that relates to it.
Can't remember if this was covered before or not.... It might be kde trying to restore a prior session.
In KDE configure desktop Under the System Administration group select Startup and shutdown Then Session management. Then in the on login section check the start with empty session.
Then log out. Maybe reboot, IDK. somehow empty /tmp Then log in.
Then remember to change this setting to what ever you had before.
Well that seems to have fixed it, but it seems a bit draconian and it doesn't tell me where the problem was. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/16/2016 04:17 AM, Anton Aylward wrote:
On 11/15/2016 07:27 PM, John Andersen wrote:
On 11/15/2016 04:02 PM, Anton Aylward wrote:
It's within KDE and within the start-up, but I can't find anything in the .kde4 tree that relates to it.
Can't remember if this was covered before or not.... It might be kde trying to restore a prior session.
In KDE configure desktop Under the System Administration group select Startup and shutdown Then Session management. Then in the on login section check the start with empty session.
Then log out. Maybe reboot, IDK. somehow empty /tmp Then log in.
Then remember to change this setting to what ever you had before.
Well that seems to have fixed it, but it seems a bit draconian and it doesn't tell me where the problem was.
Stuck Fart Problem. When KDE restarts with the session management setting set to restore previous session it will launch each program that was running at the last shutdown. Yours just happened to shut down with something still running that was making a mess at the time. Once I traced this to some obscure node in a hidden kde directory where a list of processes was stored which get restarted at the next boot. It hurt my brain at the time and not something I want to dig into again, till second cup of coffee at least. Some time ago this used to be in ~/.kde4/share/config/ksmserverrc (I think) but that seems obsolete now. Typical KDE halfassed documentation: https://userbase.kde.org/System_Settings/Startup_and_Shutdown -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
My problem with the pollution of /tmp by the rogue ghostscript process came about because I was trying to make a PDF out of a PNG and the process hung and the machine hung and I had to reboot.... You saw the consequences. John was insightful This PNG is 1860 x 2048, 8-bit/color RGB, non-interlaced. I tried printing via opening this with gwenview using its 'print image' with the print to PDF option. This is a pretty large and non-standard aspect ratio. It is a sizeable mindmap. unless you've got a large rotary printer this isn't going to be readable as a single sheet. Its readable at "B2" size. I have a number of reasons for wanting to have this in another format. Perhaps it might be smaller than its current 3Meg! PDF can be protected in a number of ways. Any other suggestions for how I can render this? Do I *have* to go via ghostscript? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/11/2016 à 13:49, Anton Aylward a écrit :
My problem with the pollution of /tmp by the rogue ghostscript process came about because I was trying to make a PDF out of a PNG and the process hung and the machine hung and I had to reboot.... You saw the consequences. John was insightful
This PNG is 1860 x 2048, 8-bit/color RGB, non-interlaced.
something like convert -resize 1920x1920 file.png file.pdf jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2016 07:54 AM, jdd wrote:
Le 17/11/2016 à 13:49, Anton Aylward a écrit :
My problem with the pollution of /tmp by the rogue ghostscript process came about because I was trying to make a PDF out of a PNG and the process hung and the machine hung and I had to reboot.... You saw the consequences. John was insightful
This PNG is 1860 x 2048, 8-bit/color RGB, non-interlaced.
something like
convert -resize 1920x1920 file.png file.pdf
Gee WOW! That works well! Thank you. I never saw any mention of PDF in the ImageMagic docco that I read. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-17 13:49, Anton Aylward wrote:
My problem with the pollution of /tmp by the rogue ghostscript process came about because I was trying to make a PDF out of a PNG and the process hung and the machine hung and I had to reboot.... You saw the consequences. John was insightful
This PNG is 1860 x 2048, 8-bit/color RGB, non-interlaced.
I tried printing via opening this with gwenview using its 'print image' with the print to PDF option.
It may be a problem with gwenview. Or with the version in 42.2. Try another program that can print to file. Even Libre Office! It has its own convert to PDF feature. As jdd says, "convert" is a possibility. Maybe Gimp. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-16 01:02, Anton Aylward wrote:
So yes, it was a postscript "ghostscript" process, which doesn't tell me anything I didn't already know. As I said, this was an artefact of an aborted attempt to print a postscript file from within Gwenview.
Print! Why didn't you say that before!? Run "lpq -a" to find print jobs, then kill them all. Print jobs survive a reboot. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2016 07:29 PM, Carlos E. R. wrote:
On 2016-11-16 01:02, Anton Aylward wrote:
So yes, it was a postscript "ghostscript" process, which doesn't tell me anything I didn't already know. As I said, this was an artefact of an aborted attempt to print a postscript file from within Gwenview.
Print! Why didn't you say that before!?
Run "lpq -a" to find print jobs, then kill them all.
Print jobs survive a reboot.
I know that. It was the first thing I though of. No, there's nothing in the queue. If there was it would start BEFORE I started KDE. Print queue is a system function, not something inside KDE. This only happens when I start KDE. And yes I've been in to the systemsetting -> Startup & shutdown (aka 'session management') and there's nothing in the list of process to run on start except for the dropbox start and fetchmail. There nothing in the .bash* or .profile to account for this either. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-16 01:51, Anton Aylward wrote:
On 11/15/2016 07:29 PM, Carlos E. R. wrote:
Print jobs survive a reboot.
I know that. It was the first thing I though of.
No, there's nothing in the queue. If there was it would start BEFORE I started KDE. Print queue is a system function, not something inside KDE.
:-(
This only happens when I start KDE.
And yes I've been in to the systemsetting -> Startup & shutdown (aka 'session management') and there's nothing in the list of process to run on start except for the dropbox start and fetchmail.
There nothing in the .bash* or .profile to account for this either.
Ok, then start a text console before starting KDE, and there in a loop run something that writes the process list to a file. Let me see. Something like echo > process.list while true { ps afx >> process.list echo "===============" >> process.list echo >> process.list sleep 1 } The while part is not correct for bash, but you get the idea. :-} The "afx" is for learning what is starting gs. I hope. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
This morning seems particularly acute. It keeps restarting! So I captured what was going on. anton 11436 2298 0 06:31 ? 00:00:00 kdeinit4: kio_file [kdeinit] file local:/run/user/501/ksocket- anton 11464 2298 51 06:31 ? 00:00:00 kdeinit4: kio_thumbnail [kdeinit] thumbnail local:/run/user/50 anton 11465 11464 99 06:31 ? 00:00:00 gs -sDEVICE=png16m -sOutputFile=- -dSAFER -dPARANOIDSAFER -dNOPAUS Sorry, my screen wrapped at that point and anton 2298 1 0 06:19 ? 00:00:03 kdeinit4: kdeinit4 Running... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
This morning seems particularly acute. It keeps restarting! So I captured what was going on. anton 11436 2298 0 06:31 ? 00:00:00 kdeinit4: kio_file [kdeinit] file local:/run/user/501/ksocket- anton 11464 2298 51 06:31 ? 00:00:00 kdeinit4: kio_thumbnail [kdeinit] thumbnail local:/run/user/50 anton 11465 11464 99 06:31 ? 00:00:00 gs -sDEVICE=png16m -sOutputFile=- -dSAFER -dPARANOIDSAFER -dNOPAUS Sorry, my screen wrapped at that point and anton 2298 1 0 06:19 ? 00:00:03 kdeinit4: kdeinit4 Running... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-15 12:15, Anton Aylward wrote:
Last week I tried creating a postscript file from a .PNG file that I had open with Gwenview.
What openSUSE release?
I've gone in via systemsettings and I can't see a startup job that would account for this; I only have a dropbox start and a video setting.
It can be a session saved application that doesn't display.
I run a 'ps' and I can't see what might be responsible.
Any suggestions as to where I should look to see what's responsible for this?
If you know the name of one of those created files (not a pattern), you can try this (before the file is created): # auditctl -w /tmp/file (1) # auditctl -e 1 and then watch the logs... (1) It needs -p or -k, and I'm unsure which. See auditctl(8) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Anton Aylward wrote:
Last week I tried creating a postscript file from a .PNG file that I had open with Gwenview.
For some reason it didn't work out, it hung and dragged the machine down and I couldn't kill it and had to reboot.
Not being able to kill a process usually indicates a hardware problem or a kernel (often driver) bug.
Since then, as I reboot the machine each morning,
??? That sounds more like a Windows box than a linux box. Why reboot so often? Unless I'm replacing my kernel, my linux box manages over 60 days uptime...
I find that after a few minutes /tmp fills us with a few THOUSAND GS_* files. Most are empty, a few are a round 10K or so. This paralyses other activities. They are owned by 'anton' -- of course.
Why would it paralyze your computer? Cpu, disk, or what? For what to try, change anton's TMP to point to another location -- verify it is being used for these gs_ files (ghostscript maybe?). Then make it read-only and see what processes complain... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward
-
Bernhard Voelker
-
Carlos E. R
-
Carlos E. R.
-
jdd
-
John Andersen
-
Linda Walsh