Timeline for How can I create a stand alone APP to run a terminal command
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:45 | history | edited | CommunityBot |
replaced http://apple.stackexchange.com/ with https://apple.stackexchange.com/
|
|
Nov 30, 2015 at 20:54 | answer | added | svth | timeline score: 1 | |
Mar 8, 2013 at 19:11 | answer | added | Bibou | timeline score: 1 | |
Mar 8, 2013 at 15:50 | vote | accept | Mort | ||
Mar 8, 2013 at 2:49 | answer | added | Daniel♦ | timeline score: 5 | |
Mar 7, 2013 at 3:03 | answer | added | bispymusic | timeline score: 5 | |
Mar 6, 2013 at 23:54 | answer | added | historystamp | timeline score: 0 | |
Mar 5, 2013 at 18:43 | comment | added | Mort | On some Mac's in our company due to various reasons (there are a few) the scripts may be delayed but up to as much as a couple of months to execute. | |
Mar 5, 2013 at 18:38 | comment | added | nohillside♦ |
Out of curiosity and assuming the given example (sudo periodic ) is the intended command: Why do you want the user to able to kick this off manually? OS X runs this automatically for you already (and even remembers to run it later if the computer was turned off at the pre-defined time).
|
|
Mar 5, 2013 at 17:47 | comment | added | Mort | I do not need users to see a terminal window and I would prefer to have a standalone .app vs a .command | |
Mar 5, 2013 at 17:43 | history | edited | Mort | CC BY-SA 3.0 |
Clarified question
|
Mar 5, 2013 at 17:40 | comment | added | zwerdlds | What specifically in the linked response is not appropriate for your usage other than the actual command? | |
Mar 5, 2013 at 17:35 | history | asked | Mort | CC BY-SA 3.0 |