storage series
Some of the content is mildly dated, but this series of posts a few years ago is still something I refer to quite often:
fighting the lack of good ideas
Some of the content is mildly dated, but this series of posts a few years ago is still something I refer to quite often:
I’ve recently been asked by several people to investigate websites (especially e-commerce ones) for reliability/legitimateness.
Thought someone else may find my process useful, and/or have some ideas on how to improve it ?
So here goes:
whois <domain.tld> | less
Creation Date: 2006-02-22T01:12:10Z
)Registry Expiry Date: 2023-02-22T01:12:10Z
)NS3.PAIRNIC.COM
)http://www.pairdomains.com
)Pair Domains
)Reviewing these items usually takes me about 2-3 minutes.
It’s not foolproof (after all, better fools are invented every day), but it can give you a good overview and relative confidence level in the site in question.
I’ve been running an M1-powered MacBook Pro since late April.
Here’s my experience so far: it Just Works™
That’s it
That’s the tweet
Want more? Sure!
Battery life is bonkers-awesome! I can run for over a full working day with my VDI client, YouTube, web browser sessions, ssh, several chat apps (including video and audio chat) sans being plugged in.
This is the laptop we’ve all wanted.
I half wish (or is it “wish”) I’d gone with the 5G-enabled, M1-powered iPad Pro instead … but this laptop is phenomenal.
There has been nothing I’ve wanted to do in the last 3 months that I could not do with this machine.
Kudos, Apple.
Kudos.
It took Apple 5.5 (or 6, if you count last week as really hitting it) years to introduce what I called the MacBook Flex back in 2015.
With the 13″ MacBook Pro available in an M1-powered edition (which is so much better than the top-end MBP from 2019…it’s not even funny), and now a 5G-enabled iPad Pro running on the M1 … it’s here.
A couple weeks ago some folks in the splunk-usergroups.slack helped me using accum
and calculating with a modulus to make a grid menu from a list.
My original search had been along the lines of:
| inputlookup mylookup
| stats count by type
| fields - count
| transpose
| fields - column
Which was great … until my list grew more than about 12 entries (and scrolling became a pain).
A couple folks here helped me flip it to this format:
| Inputlokup mylookup
| stats count by type
| eval num=1
| accum num
| eval num=num-1
| eval mod=floor(num/12)
| eval type.{mod}=type
| fields - mod num type count
| stats list(*) as *
Which works awesomely.
Unless the modulus value (currently 12) gets too small (if the total list grows to more than modval^2 .. each individual box is no longer in alphabetical order (and then alpha from box to box).
So I made this modification so that regardless of the size of the list, the grid will automanage itself:
| inputlookup mylookup
| stats count by type
| eventstats count as _tot
| eval modval=ceil(sqrt(_tot))
| eval num=1
| accum num
| eval num=num-1
| eval mod-floor(num/modval)
| eval type.{mod}=type
| fields - modval mod num type count
| stats list(*) as *
Dunno if that’ll help anyone else, but wanted to share-back that self-managing aspect I added in case anyone was interested