ｈａｃｋｍｕｄ | Bugs | Move sys.upgrades and related scripts to a new user

◢███◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢██◤ ◢███◤ ◢██◤ ◢██◤ ◥██◣ ◥███ ◢█████◣ ◢████████◤ ◢███████◤ ◢██◤ ◢██◤ ◢██◤ ██◣ ███ ◢███████◣ ◢██◤ ◢██◤ ◢██◤ ◢███████◤ ◢██◤ ███ ███ ◢██◤ ◢██◤ ◢████████◤ ◢██◤ ◢█████◣ ◢██◤ ███ ███ ◢██◤ ◢██◤ ◢██◤ ███◤ ◢██◤ ◢██◤ ◢██◤◥███◣ ◢██◤ ███ ◥██ ◢██◤ ◢██◤ ◢████████◤ ◢███████◤ ◢██◤ ◥███◣ ◢██◤ ███◣ ◥██◣ ◢██◤ ◢███◤ ◢███◤ ◢███◤ ◢██◤ ◢██◤ ◢█████████◤ ◢██◤ ◢█████████◤ ◢██◤ ◢██◤ ◢██◤ ████◤ ◢██◤ ◢██◤◢█◤◢██◤ ◢██◤ ◢██◤ ◢██◤ ███◤ ◢██◤ ◢██◤ ◢██◤ ◢████████◤ ◢█████████◤ ◢██◤ ◢██◤ ◢██◤ ◢████████◤ ◢█████████◤ ◢███◤

dtr

{180103.2007}

Right now, the sys user has scripts serving 3 main purposes: 1) Scripts that actually relate to your system: sys.init, sys.specs, sys.status, sys.access_log, sys.loc, sys.breach 2) PVP scripts: everything in scripts.sys 3) upgrade stuff: sys.upgrades, sys.manage, sys.cull, sys.upgrade_log, sys.xfer_upgrade_to This is rather confusing, and the naming isn't clear. Many new users don't realize sys.cull is how you delete upgrades because it sounds like it culls your system, not your upgrades. Ditto with sys.manage. Only people who were around when those were part of sys.upgrades understand what they are and why they are on sys. My proposal: take the last category, upgrade stuff, and move it to a new trust user (I propose "ups" so that no scripts need to get longer to accommodate the change) as follows: sys.upgrades -> ups.info sys.manage -> ups.manage sys.cull -> ups.cull sys.upgrade_log -> ups.log (or ups.transactions or ups.upgrade_log) sys.xfer_upgrade_to -> ups.xfer_upgrade_to This would more closely mirror accts, and remove a clearly defined set of scripts off the over-used sys user (internally, they could still operate via sys.lib -- no database migration needs to occur), and leave sys for actual sys stuff and pvp stuff (which both feel at home on sys).