ICE

Please login or register.

Login with username, password and session length
Advanced search  

News:

ICETCP.PRO and ICETCP.PLUS are compatible with Windows 11!

Author Topic: icelp 5.1.26 and CentOS 7  (Read 2056 times)

mercuryelectronics

  • Newbie
  • *
  • Posts: 2
  • Place Personal Text Here
icelp 5.1.26 and CentOS 7
« on: September 08, 2015, 12:16:53 pm »

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
Logged

Bob

  • Administrator
  • Ice Artist
  • *****
  • Posts: 1607
Re: icelp 5.1.26 and CentOS 7
« Reply #1 on: September 21, 2015, 01:09:51 pm »

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.
Logged
 

Page created in 0.01 seconds with 21 queries.