Re: Printing and silly students
- To: email@example.com
- Subject: Re: Printing and silly students
- From: Adam Aube <firstname.lastname@example.org>
- Date: Fri, 15 Apr 2005 09:04:38 -0400
- Message-id: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com>
Jonathan Lassoff wrote:
> Adam wrote:
>>CUPS keeps a log file (/var/log/cups/page_log under Debian) that contains
>>useful accounting data.
> This is almost exactly what I am looking for, and likely what I will
> use, but it isn't really super-useful. What we really need to do is find
> the user who issues the jobs, so just the IP and time right now wont do
> much unless we find the miscreant print job right away, and that doesn't
> always happen. What would be optimal is an authentication mechanism.
I have noticed on a network with Windows XP workstations and a Samba domain
controller running CUPS, the CUPS accounting log contains the authenticated
username, even though the workstations do not print through Samba.