<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Office-It on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/office-it/</link>
    <description>Recent content in Office-It on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/office-it/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Print Quotas on Linux in 2026: Native CUPS Limits vs PyKota vs SavaPage</title>
      <link>https://www.pistack.xyz/posts/2026-11-19-print-quota-management-cups-pykota-savapage/</link>
      <pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-19-print-quota-management-cups-pykota-savapage/</guid>
      <description>&lt;p&gt;A shared office printer without accounting is a money leak with a paper tray. One department prints 4,000 pages of draft invoices, another prints nothing, and at the end of the quarter nobody can say who consumed the toner budget. The fix is not a bigger printer — it is a quota layer, and on Linux you have exactly three realistic options: the quota attributes baked into CUPS, PyKota&amp;rsquo;s per-user accounting backend, and SavaPage&amp;rsquo;s full web-based print portal.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
