I tend to have a low attention span, so when I get a proof-of-concept like this up and running (and prove it works), even if the final results are not "polished", I then want to "call it good enough" and quickly move on to the next project.
This is me too except for the attention span. As soon as I find a solution to something I let others better it.
And as for doing something different I have done some bizarre stuff on here... <wink> /Me awaits the mickey take... ;oD
OT: Here is a small snippet for a terminal window you might like under OSX 10.14.6 on this MBP, solved and going into the Campimeter code.
Enjoy...
Last edited by wisecracker; 01-30-2020 at 03:29 AM..
Reason: Corrected the "shebang", 30-01-2020. Thanks Ravinder...
These 2 Users Gave Thanks to wisecracker For This Post:
I am interested in knowing if anyone out there has been using the BSD UNIX that underlies
MacOS X. Is this an "industrial strength" version of UNIX? Can I run X-Windows on such
a machine? How about TeXing, pythoning, PERLing or using other useful UNIX goodies
near and dear to my shrunken... (1 Reply)
1) How can I stop Vuze from reporting the following error: "Too many open files" ?
2) What directory do I need to be in to effectively utilize this command:
sudo bash -c 'ulimit -n 8192; sudo -u username ./azureus' ?
3) Is this the maximum number of files that I can allot to Vuze on OS X... (1 Reply)
Dear all,
I use awk quite a bit for data wrangling ... today I find weird behavior that I cannot wrap my head around.
if I execute the following command (simplified to illustrate the behavior ... nothing to do with the real command)
bash-3.2$ awk... (3 Replies)
why,just beacuse that its the bottom layer uses a small amount of bsd code? In my opinion, macos and Unix are completely different. The directories are long directory structures. For example, /application, /system, /user, /volumes, etc. are completely different from the traditional /bin/ /sbin... (5 Replies)
Interestingly Apple has decided to switch the default shell for new users from bash to zsh in MacOS Catalina (10.15)
Use zsh as the default shell on your Mac - Apple Support
Another interesting fact is that Catalina also comes with /bin/dash (5 Replies)
Hi all...
This was the original code I created to expand a terminal on the fly using Python 2.6.x to the now 3.8.0 without modification under OSX 10.7.5.
I had no idea at the time that the MBP terminal could be full screen until here:... (0 Replies)
Discussion started by: wisecracker
0 Replies
LEARN ABOUT MOJAVE
assetcachemanagerutil
AssetCacheManagerUtil(8) BSD System Manager's Manual AssetCacheManagerUtil(8)NAME
AssetCacheManagerUtil -- control the macOS Content Cache
SYNOPSIS
AssetCacheManagerUtil [-a|--all] [-j|--json] [-l|--linger] command
DESCRIPTION
AssetCacheManagerUtil controls the macOS Content Cache. AssetCacheManagerUtil must be run by root except as noted below. The options are:
-a|--all Show all events, not just the end result of the specified command.
-j|--json Print results in machine-parseable JSON format to stdout.
-l|--linger Linger after completing command, to show other events.
The commands are:
activate Activates the content cache. Content caching is deactivated by default. After you activate content caching, restart devices
on your network to take advantage of content caching immediately. Devices on your network will discover this content cache
over time. Devices that are restarted will use this content cache immediately.
deactivate Deactivates the content cache.
isActivated Reports the content cache's activation status. Does not require root.
canActivate Reports whether the content cache is eligible for activation. Does not require root.
flushCache Flushes the content cache.
flushPersonalCache
Flushes all personal (iCloud) content from the content cache.
flushSharedCache
Flushes all shared (non-iCloud) content from the content cache.
status Reports the content cache's status. Does not require root.
settings Reports the content cache's settings. Does not require root.
reloadSettings
Forces the content cache to reload its settings.
moveCacheTo path
Moves the cache to path. The path must end with /Library/Application Support/Apple/AssetCache/Data. The contents of path are
deleted and replaced with the cache.
absorbCacheFrom path read-only|and-destroy
Imports the cache from path. The path must end with either /Library/Application Support/Apple/AssetCache/Data or
/Library/Server/Caching/Data. If the last argument is read-only the cache at path is not modified, otherwise it is emptied.
This command only starts the absorption, which proceeds and finishes in the background.
SEE ALSO
System Preferences > Sharing > Content Caching, AssetCache(8), AssetCacheLocatorUtil(8), AssetCacheTetheratorUtil(8)macOS June 1, 2019 macOS