tech11 wrote:
> "Nico Kadel-Garcia" <nkadel@comcast.net> дÈëÏûÏ¢ÐÂÎÅ:__idnVAVAY7SOzDZnZ2dnUVZ_rGdnZ2d@comc ast.com...
>> Jean-David Beyer wrote:
>>> tech11 wrote:
>>>> Hello everyone,
>>>>
>>>> I need to backup the files when printing from graphics window, but
>>>> how should I do? Normally if printing from the command window, I may
>>>> check and backup it, but from graphics, I have no any idea to do.
>>>>
>>> Are you confused or am I? I backup my files every marningat about 1
>>> AM when I am normally asleep and my monitor is turned _off_ so it
>>> does not really matter if I am running a "graphics window" or not,
>>> since I am at that time running neither a "graphics window" nor a
>>> virtual terminal.
>>>
>>> What does a display have to do with running backups (that I normally
>>> run as just a routine _cron_ job)?
>> It sounds like he wants to take storable snapshots, as well as or instead
>> of actually printing.
>>
>
> Well, maybe I should describe my option aim clearly. Normally persons print
> something freely and have no more record or log to check, it's dangerous to
> us. Since someone print out our technology drawing and make it open, so I
> wanna find a way to keep the print record and check the printing data when
> need. If printing from command, it's easy to backup the printing data and
> record the operation at the same time. But if he print from the software
> window, normally there's one menu to print directly, I have no way to keep
> the tail. Is there any way to keep the printing data's snapshot? either
> other ways to do?
>
> Maybe you'll tell me to control the files' permission, but sometimes it's
> difficult to distinguish them. Some files need to be refered and have to
> keep readable to staff inside, but you mayn't ensure the printing copy
> diffusing to outside. That's my intention to ensure the control, at least I
> may have a way to find the leak hole.
>
> Have a pleasure weekend!
>
> B.R.
>
> Joffre
>
>
On *nux, at least with the older print systems I am used to - I am pre
CUPS or whatever it is called - every print job does finally go to a
script somewhere that is responsible for various bits of processing -
even if its just throwing a control character out to cause the printer
to linefeed at the end of the job, and these are not hard to alter to
log who printed what, or even to load up a copy of all the print jobs
somewhere else.

You need to identify the chain of scripts that are involved when
anything gets printed, and find a suitable place to modify and split the
print job to keep copies.

Be warned however, that these are usually VERY large indeed.