This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 58
outset folders not created during the install #110
Comments
I recommend looking at the new swift based outset (https://github.com/macadmins/outset/releases). It'll make your life immeasurably better. But to answer the question, the folders get created if they are missing, the first time outset runs. See the wiki for info on deploying your custom scripts. https://github.com/chilcote/outset/wiki/Customize#adding-your-custom-items |
Thank you! That version works and creates the folders. I’m still not able to run my shell script it’s just this – which I tried in both login-every and login-privileged-every – the logs says permissions are incorrect and must be 755, so I used chmod to change it to 755, but still saying permissions are incorrect, must be owned by root with x755. Can you tell me what I’m doing wrong?
#!/usr/bin/env bash
/usr/bin/security authorizationdb write system.preferences.printing allow
…________________________________________
Karen Bassett
School of Education
Department of Technology and Media Services
5525 WWPH
412-624-4116
***@***.******@***.***>
From: Joseph Chilcote ***@***.***>
Date: Saturday, September 2, 2023 at 3:48 PM
To: chilcote/outset ***@***.***>
Cc: Bassett, Karen ***@***.***>, Author ***@***.***>
Subject: Re: [chilcote/outset] outset folders not created during the install (Issue #110)
I recommend looking at the new swift based outset (https://github.com/macadmins/outset/releases). It'll make your life immeasurably better.
But to answer the question, the folders get created if they are missing, the first time outset runs. See the wiki for info on deploying your custom scripts. https://github.com/chilcote/outset/wiki/Customize#adding-your-custom-items
—
Reply to this email directly, view it on GitHub<#110 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXPMTAEHIOXG4UGGT2U6Y4DXYOER5ANCNFSM6AAAAAA4IYTR2U>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Is it owned by root? What does |
In trying to fix it, I made it worse, now -- I just can't seem to get the right permissions to put a shell script in the login-every folder.
I changed to chmod o+rw which I thought should work, the GUI get info shows the user has rw and wheel has r.
***@***.*** login-every % /usr/local/outset/outset --login-every
ERROR: Permissions for /usr/local/outset/login-every/AllowPrinting.sh are incorrect. Should be owned by root and with mode x755
ERROR: Unable to create log file at /usr/local/outset/logs/outset.log
ERROR: Bad permissions: /usr/local/outset/login-every/AllowPrinting.sh
ERROR: Unable to create log file at /usr/local/outset/logs/outset.log
***@***.*** login-every % ls -la
total 8
drwxr-xr-x 3 root wheel 96 Sep 3 11:54 .
drwxr-xr-x 14 root wheel 448 Sep 3 11:44 ..
…-rwxr-xr-x@ 1 user wheel 341 Sep 2 14:23 AllowPrinting.sh
***@***.*** login-every % chmod 755 /usr/local/outset/login-every/AllowPrinting.sh
***@***.*** login-every % /usr/local/outset/outset --login-every
ERROR: Permissions for /usr/local/outset/login-every/AllowPrinting.sh are incorrect. Should be owned by root and with mode x755
ERROR: Unable to create log file at /usr/local/outset/logs/outset.log
ERROR: Bad permissions: /usr/local/outset/login-every/AllowPrinting.sh
ERROR: Unable to create log file at /usr/local/outset/logs/outset.log
***@***.*** login-every % ls -la
total 8
drwxr-xr-x 3 root wheel 96 Sep 3 11:54 .
drwxr-xr-x 14 root wheel 448 Sep 3 11:44 ..
-rwxr-xr-x@ 1 user wheel 341 Sep 2 14:23 AllowPrinting.sh
________________________________________
Karen Bassett
School of Education
Department of Technology and Media Services
5305 WWPH
412-624-4116
***@***.***
________________________________
From: Joseph Chilcote ***@***.***>
Sent: Sunday, September 3, 2023 8:20 AM
To: chilcote/outset ***@***.***>
Cc: Bassett, Karen ***@***.***>; Author ***@***.***>
Subject: Re: [chilcote/outset] outset folders not created during the install (Issue #110)
Is it owned by root? What does la -la /path/to/script look like?
—
Reply to this email directly, view it on GitHub<#110 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXPMTAD2ZQY7OLVDAHMCZMTXYR72BANCNFSM6AAAAAA4IYTR2U>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I don't see the permissions of the script in that output. Also I think you'll want to put this in boot-every or the login privileges one since I think the security commands might need root? Also it's trying to write to the log file and doesn't have permission for that either looks like. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was installing an older version with JAMF and noticed the sufolders are not being created, I just tried the new version on both Ventura and Monterey (freshly wiped and reinstalled OS) and ran the lated v 3 installer and there are no folders in the outset folder. I want to run a scrip to allow non-admins to add printers and remove wireless networks, and using login-every seems to be the best way to go,
The text was updated successfully, but these errors were encountered: