----- Original Message -----

Hi John, (Cc:ing this also to x2go-dev)

On Fr 08 Apr 2011 15:38:32 CEST "John A. Sullivan III" wrote:

...

Phil has patched the x2goprint script to fix the disappearing print job problem and will be posting those patches to the dev list shortly.

Please note that I have also patched x2goprint that's stil pending for inclusion in x2goserver (we will drop the separate x2goprint project): http://code.x2go.org/gitweb?p=x2goserver.git;a=shortlog;h=refs/heads/pending...

The patch makes x2goprint usable on NFS mounted home directories.

Furthermore, I guess it needs patches of cups-x2go as well. Because there are indeed some lost jobs and also zombie files that collect up (e.g. in /).

I guess the best approach for providing patches and share your work would be to work on the code base in Git on code.x2go.org.

Greets, Mike

Mike,

what I found was that the .ready file was sometimes not created on the SSHFS mounted spool directory; and as it was not there the X2Go print dialogue box would not be shown. I basically changed the code to the following:

if( $mounts=~m/$spooldir/) { move ("$printdir/$file", "$spooldir") or die "$!: Can't rename $file to $homedir/.x2go/C-$session/$file"; $file $spooldir\"");

 my $counter = 0;
 while ( ! -f "$spooldir/$file.ready" && $counter < 10 )
 {
    open (RFILE,">$spooldir/$file.ready");
    print RFILE "$file\n$title";
    close (RFILE);
    $counter = $counter + 1;
 }
 if ( $counter > 1 ) { syslog("info", "Failed to write ready file - Count $counter - C-$session/$file"); }

} else { unlink("$printdir/$file"); }

So at least now it will try a few times and if it does file then a syslog message is produced which OSSEC picks up and alerts us on. I should add that the actual PDF file does make it to the physical client computer. Is that what you have seen ?

Thanks, Phil