I'm a web sysop and support engineer. My skills are mainly in back-end: Java, Linux, Python, PostgreSQL, Git, and GitLab. Currently I'm learning front-end skills: JavaScript, and Ruby.
I'm a web sysop and support engineer. My skills are mainly in back-end: Java, Linux, Python, PostgreSQL, Git, and GitLab. Currently I'm learning front-end skills: JavaScript, and Ruby.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
AWS Alpha Tester (via Adobe)
Consultant to several Fortune-500 companies, government municipalities, school districts , and international entities in Enterprise-grade Asset Management projects.
Here's one more I'm using sometimes:
So here I'm redirecting STDERR to the address of STDOUT, which is a file called "out_and_err.txt".
I think that in recent bash and zsh, one can use
This is my favourite "shut up, I don't want to see any output, even if it fails, just do, or don't do, the thing" shortcut:
I think you have a small typo here.
Shouldn't it read
Thank you, fixed 😁
You're welcome.
Another really useful redirection-related BASHism:
<( ):Useful if, say, you want to check to see if a local file and an S3-hosted file are the same:
Similarly, can be used for things like
diffing two streams:Another one people don't seem to use much is
>|which will overwrite a file even ifnoclobberis on.Makes truncating a breeze!
|> logfile.logI never looked these up before, though I use most of them almost everyday 😁
Thanks Pierson!
Haha, I was in the same boat!