Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mercuryelectronics]

We are looking at upgrading our Linux server from CentOS 6.2 to CentOS 7.  On the 6.2 server the output path for icelp files for iceprint1 is /usr/tmp/iceprint1/icelp_jobs.  On CentOS 7 the file path is /usr/tmp/systemd-private-2LHMv3/tmp/iceprint1/icelp_jobs.  The problem is that after a server reboot and a file sent to iceprint1 the path it now created is /usr/tmp/systemd-private-TmAVj/tmp/iceprint1/icelp_jobs.  The systemd-private-??? portion of the path is changing after a reboot and therefore the client's setting do not match.  I tried looking at the icelp file in the /usr/lib/cups/backend folder and it looks like it should write to /usr/tmp.  Any ideas as to why the extra folder level of systemd-private-???/tmp is being added. 

Thanks,
Josh

[Bob]

We are looking at upgrading our Linux server from CentOS 6.2 to CentOS 7.  On the 6.2 server the output path for icelp files for iceprint1 is /usr/tmp/iceprint1/icelp_jobs.  On CentOS 7 the file path is /usr/tmp/systemd-private-2LHMv3/tmp/iceprint1/icelp_jobs.  The problem is that after a server reboot and a file sent to iceprint1 the path it now created is /usr/tmp/systemd-private-TmAVj/tmp/iceprint1/icelp_jobs.  The systemd-private-??? portion of the path is changing after a reboot and therefore the client's setting do not match.  I tried looking at the icelp file in the /usr/lib/cups/backend folder and it looks like it should write to /usr/tmp.  Any ideas as to why the extra folder level of systemd-private-???/tmp is being added. 

Thanks,
Josh

It looks like the systemd rewriting of the tmp directory needs to be either shutoff or avoided.
You could likely create a directory, say /var/spool/jriver and use that in place of the /usr/tmp in the /usr/lib/cups/backends/icelp file and also in the users configuration for ICELP on their PC.