ZM OpenSuse 13.1 /tmp directory
Posted: Wed Jan 08, 2014 11:52 am
I have been running ZM for a couple of years on OpenSuse without any problems. This last weekend I upgraded my system to OpenSuse 13.1 and have run into a slightly strange problem which I can't seem to fix.
The problem manifests itself because I use a background script to check whether ZM is running and this script uses a zmpkg.pl status request, which in turn calls zmdc.pl check. I ran zmdc.pl under perl diagnostics and checked where it was looking for the socket and as expected it said /tmp/zm - I didn't change the default when I compiled ZM. However, even with the console saying ZM is running zmdc.pl check says stopped and there is no zmdc.pl file in /tmp/zm.
When I did a find for zmdc.sock I found another copy in /tmp/systemd-private-v1Apw1/tmp/zm when the console says running and again the file disappears when I ask the console to stop.
I cannot work out why the console and command line are using two different tmp directories.
Has anyone else seen this and any idea how to sure it?
The problem manifests itself because I use a background script to check whether ZM is running and this script uses a zmpkg.pl status request, which in turn calls zmdc.pl check. I ran zmdc.pl under perl diagnostics and checked where it was looking for the socket and as expected it said /tmp/zm - I didn't change the default when I compiled ZM. However, even with the console saying ZM is running zmdc.pl check says stopped and there is no zmdc.pl file in /tmp/zm.
When I did a find for zmdc.sock I found another copy in /tmp/systemd-private-v1Apw1/tmp/zm when the console says running and again the file disappears when I ask the console to stop.
I cannot work out why the console and command line are using two different tmp directories.
Has anyone else seen this and any idea how to sure it?