231–240 of 244 posts
Earlier quoted context omitted.
I'm a bit green when it comes to db back ups. Do you have anything I can read on this approach it sounds really promising but I don't think I understand it?
The docs are good: https://www.postgresql.org/docs/current/continuous-archiving...
They are I would not have expected the DB docs to go into that level of conceptual detail
Earlier quoted context omitted.
Im no expert but my recent conclusion from writing an ordering system is customers can instruct their banks to roll back many payments a month or even a year after the fact So actual ACID transactional consistency requires a year. So after basic checks just say you'll give them what they want and accept payment -- since you'll need failure recovery anyway for lack of delivery, refunds, acts of God etc So accept and p…
The idea I've seen repeated here a lot is to aim for strong consistency internal to your system, even though the real world/things external to your system will be eventually consistent. So the inventory create order interactions are internal and can be strongly consistent, while the realities of the banking system are external and will be eventually consistent. Just because you can't make everything strongly consiste…
Earlier quoted context omitted.
Export-Csv was introduced in PowerShell v1.0: https://social.technet.microsoft.com/wiki/contents/articles/... > but it's not as simple as `ssh user@host` It is literally that simple. Nay, simpler , because authentication is automatic and secure: Enter-PSSession 'hostname' Oh, I'm sorry... too verbose and readable. etsn 'hostname' > since bash is a collection of utilities[1] and doesn't require deep integration with t…
This is a great discussion from everyone! I have learned a lot about Powershell here, so thank you! That said, the comparison to a homogenous windows env and a mixed flavor linux environment is disingenuous. Using multiple flavors of linux is just multiple OSes, of which Windows would be another. The best advice here is to stick to one flavor of linux, which should be possible because there are no licensing fees!
Single-choice vendors like Microsoft or Apple remove this variability, which is a big benefit at the scale of large enterprise or “entire ecosystems”.
Linux is too flexible, and the inevitable consequence of this is that I have customers that each have a dozen incompatible variations in production.
Even if each customer had precisely one version of one distro, my scripts wouldn’t be safely portable between them if they don’t happen to pick the same distro!
I’ve got decade-old complex PowerShell scripts I’ve reused across a dozen unrelated customers. That’s a significant benefit.
So the comparison is fair.
Earlier quoted context omitted.
This is a great discussion from everyone! I have learned a lot about Powershell here, so thank you! That said, the comparison to a homogenous windows env and a mixed flavor linux environment is disingenuous. Using multiple flavors of linux is just multiple OSes, of which Windows would be another. The best advice here is to stick to one flavor of linux, which should be possible because there are no licensing fees!
There is an often overlooked downside to “options”: it means that even well-meaning people will pick inconsistent things unless ruthlessly forced into compliance. Single-choice vendors like Microsoft or Apple remove this variability, which is a big benefit at the scale of large enterprise or “entire ecosystems”. Linux is too flexible, and the inevitable consequence of this is that I have customers that each have a do…
And it’s not like Microsoft doesn’t change things around between different releases of Windows. I’ve ran into just as many compatibility issues with edge case software between different versions of Windows as I have with Linux. The key is just understanding the base of your OS as well as your software. This is as true for Windows as it is Linux.
And I have Bash scripts written in the 90s, before Powershell was even a thing, that still work now. In fact one of the biggest complaints about POSIX is the age of the specification. So it’s strange that you’re talking about Powershell as if it’s unique in its compatibility promise.
I’m honestly questioning just how much experience you have in this field because you talk as if everyone misunderstands Windows yet then go on to make the exact same misconceptions about Linux (and POSIX in general).
Earlier quoted context omitted.
> But the above is the general gist of it. It's not even remotely the gist of it. The output of that is formatted (pretty-printed) text, not CSV. You won't know which computer the output came from. You can't use this output in any meaningful way. It's not useful to the business . ssh can't connect to multiple servers at once (other tools like multissh can). However, most such tools aren't designed for and aren't capa…
> It's not even remotely the gist of it. The output of that is formatted (pretty-printed) text, not CSV. You won't know which computer the output came from. You can't use this output in any meaningful way. It's not useful to the business. You can add all of that easily. Printing hostnames or turning text to CSV isnt a hard job on any computer. I was doing this in the 90s on Windows, years before Powershell. And on pr…
It is actually shockingly difficult.
Less talk, more script source, paste below please.
Do test it first though, several people have submitted hilariously incomplete, invalid, or partial solutions.
Earlier quoted context omitted.
> It's not even remotely the gist of it. The output of that is formatted (pretty-printed) text, not CSV. You won't know which computer the output came from. You can't use this output in any meaningful way. It's not useful to the business. You can add all of that easily. Printing hostnames or turning text to CSV isnt a hard job on any computer. I was doing this in the 90s on Windows, years before Powershell. And on pr…
> Printing hostnames or turning text to CSV isnt a hard job on any computer. It is actually shockingly difficult. Less talk, more script source, paste below please. Do test it first though, several people have submitted hilariously incomplete, invalid, or partial solutions.
No it isn’t. The problems you describe are literally what the Unix command line was invented to solve, way back in the 70s. And what every other pipe-supporting command line shell, PS included, has been inspired by since.
If you want to talk about which shell you personally prefer writing scripts in, then that is a different matter. I have zero issue with people preferring Powershell (heck, Linux can run PS these days). I even wrote my own shell because I felt I could do better than Bash. But don’t make bullshit up like “Linux can’t print host names nor CSV” when that’s basically the MVP for any command line interface.
> Less talk, more script source, paste below please. Do test it first though, several people have submitted hilariously incomplete, invalid, or partial solutions.
I honestly don’t see why I should bother. I’m on my phone, cooking breakfast and playing with my kids. And it’s pretty clear you’ve already made your mind up. So I don’t see why I should give up family time to win an argument with a random internet commentator who’s clearly never going to get anything beneficial from the exchange anyways.
The fact that you don’t understand how ssh nor xargs work just demonstrates that you’re not in position to make these kinds of comparisons in the first place.
So take my word for it or don’t. I don’t really care any more. But I’m not going to interrupt morning and fire up a laptop just to write a script that you’ll instantly dismiss for whatever arbitrary and biased reason you dream up next.
Earlier quoted context omitted.
What are you talking about - Windows was always terrible for an admin. Unix was and is vastly superior when it comes to remote admin. Having used both (Powershell is powerful yes, but it's nowhere as fluid as a Unix shell).
That's just not true. It feels true to Unix admins trying to do Unix things on Windows and getting frustrated when nothing feels familiar. Let me quote the article directly: "no SSH" WinRM is roughly equivalent and superior in many ways. E.g.: It takes quite the effort to produce a report of "some setting or flag" across a fleet of servers with SSH, Bash, Sed, Awk, etc.. Now try this with PowerShell: Invoke-Command -…
but where was powershell (introduced in 2006) on unix (introduced in 2016) when admins needed it since epoch?
the tools i have learnt might have more cryptic names but they were there since the beginning.
it took microsoft an awfully long time to realize cmd.exe just wont cut it.
also powershell has no choice but to include the kitchen sink to be usable because there is little composability in the windows shell world compared to the cambrian explosion of unix utilities.
anyway, each to their own, peace.
Earlier quoted context omitted.
cat list_of_servers | parallel --tag ssh {} ps -aux The whole point of UNIX is to use independent, composable tools that speak the same interface. If the interface is space-separated values, use space-separated values. If Excel or PowerBI don't use that then don't use Excel or PowerBI.
Your boss uses Excel and doesn't like it when the reports\ read\ like\ this because you ignored his requirements. Your coworker is also angry at you now, because when he scheduled your script to run regularly, the output occasionally turns into gibberish because of inconsistent handling of special characters and error conditions, breaking automations randomly. I spotted several errors in your provided "solution", whi…
thousands of servers are managable only with orchestration solutions, this is a solved problem. the unix world also has evolved from a bash for loop to ssh into servers and read outputs.
i can solve your task in comparable time with pyinfra or ansible executing arbitrary python code on every node with not just csv output but whatever you dream up.
Earlier quoted context omitted.
Very likely you're right, as mentioned in another comment (and in the article I think) I didnt know the semantics of the backup system, I’d just tested with a couple of 400G HDDs - then the NFS endpoint I was given to replace those drives was behaving differently and a deep investigation across wide timezones and uncommunicative teams began. We have the benefit of hindsight now so things can be more clear than they w…
It's particularly nice as it allows to do point in time recovery - you can tell PostgreSQL to replay WALs up to a given point so if say corruption happened because of some code bug you could play the database to the point minute before. Backup process is two part * archive logs as they come in - PostgreSQL have hook that will run program with the WAL segment to archive so just need to put whatever you want to use to…
Your replica needs the ability to read from the WAL storage in the event that you have high transactional throughput.
If you have a low volume then maybe you've never seen it, but it's in the documentation here:
https://www.postgresql.org/docs/11/archive-recovery-settings...
Earlier quoted context omitted.
> tech lead, feature lead, mentor, cross-team liaison, steering committee member All roles that young folks dream about becoming when they grow up. Grandma: What do you want to be when you grow up, honey? Granddaughter: A CROSS-TEAM LIASON!!! Yay!!!
I mean... the whole point is that that stuff is not a titled role. It's responsibility you can choose to take on as a senior IC that helps extend your reach, influence, and visibility into what is going on elsewhere in the company, making your voice that much more valuable and insightful when you're pulled into those meeting to talk long term technical direction and strategy. I don't think it's too hard to imagine ho…
> I don't think it's too hard to imagine how to explain this in a way that might excite a child, but at the end of the day, they look to us for their cues on whether to be excited about Daddy's promotion, whether it's to "Team Lead" or "Staff Engineer".
I genuinely can’t tell if you’re serious or trolling.
Poe’s Law is in play, I guess.
Fwiw, the eyes of every child I have ever been around always glaze over whenever an adult whips out corporate speak. I think there is a good reason for this.