Also, you don't need to spawn a subshell nor feed sort via stdin in the first example :)
183 karma · joined November 9, 2019
Also, you don't need to spawn a subshell nor feed sort via stdin in the first example :)
You are basically describing modern programming.
Script Language (or scripting) is a programming language.
And about the "real" programming language you can also trap yourself googling and installing yet another library (did you read the code?) and/or reimplementing existing tools from the unix programming environment.
Is okay for one to have their own tools.
$ f() { printf "\$%s" "$1"; }
$ echo a b c | awk '{ print $(f 2) }'
His system is not very different from mine or yours. He just chose to combine the tools in a specific way.While in the awk example it is creating a hash table with all words and incrementing by the key and then printing.
There is no sorting plus printing may be buffered.
Another nice thing about /usr/bin/time is the --verbose flag which gives:
Command being timed: "ls"
User time (seconds): 0.00
System time (seconds): 0.00
Percent of CPU this job got: 0%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 1912
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 112
Voluntary context switches: 1
Involuntary context switches: 1
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
:)Take some time to learn some soft skills, just enough to be able to convince people to do stuff for you, if you are the "throw over the wall ones" I recommend to get out of your sillo and interact well with the rest of your team :)
The problem with "serverless" is this kind of attitude around it.
Seems like a really fun project.
> I only learned about MX record priorities last night haha.
Nice!
> With Postfix, the most straightforward way to run code on receiving an email seems to be through a pipe filter.
True.
Take a look into LMTP, you may be able to "read the email" directly from your rust daemon (via unix socket or tcp) :)
No, there only very few cases, such as shaving video encoding time (the one that started all this mess around "serverless")
For majority of other cases, using "(human) resource efficient" or "time saved managing servers" to justify the use of "serverless" is a plain bogus argument, since you end up shifting (best case scenario) OR spending more (worst case) time "managing the cloud's alphabet soup".
I will not even start talking about the code base mess.
I wish you all the best! Mind if I ask for the link?
> With (1), there is no need to worry about overages, but scaling the mail server might be challenging.
Honestly, quite the opposite.
1. Duplicate your MX box.
2. Duplicate your MX record.
That is it :)
> I am writing the mail processing daemon ... in Rust...
You might like to take a look in https://github.com/mailman/mailman for ideas/inspiration. It's a great tool for processing emails too, but cannot deny I'm now curious to see how one in rust will look like.
---
> Not a single post on Hacker News can use the term "serverless" without the exact same replies being posted every time.
Indeed.
> It's as if a certain portion of the HN crowd simply cannot fathom that a new term exists and is in use, and instead resort to the same, tired responses.
If was only "a certain portion/crowd" it will have no responses at all.
I see more like:
"It's as if a certain portion of the HN crowd simply cannot fathom that servers exists and is easy to use, and instead resort to the same, tired responses."
Your setup seems sane and pretty close to what would be if you want to run the same thing on a single server.
It makes the code base in the original link looks like a proprietary duct tape spaghetti :P
I just recommend setup postscreen[1] and rspamd[2].
This is the standard marketing phrase echoed to promote serverless. By experience, I don't think is valid. Packages like unattended-upgrades automates all this stuff.
Also, not being able to verify what the software is doing is scary and looks like a 10 steps backwards to me.
> 2. Since every logical component is an independent service, each scaling independently, any one single component is unlikely to become a bottle-neck while scaling. In traditional monolithic servers, you'll have to have contingency plans if you beat storage/network/CPU/RAM limits
Except when it comes with a bottle-neck by default. Running mail servers requires rather little resource.
> 3. The closest thing to this is to break up a monolithic email server into microservices and deploy them as independently scalable containers, which is a considerable engineering effort.
Why in earth? Have you seen the postfix architecture?
> Assuming this works as advertised, you can go from zero to a full blown email service for organizations with thousands of people (assuming the stated AWS limits are lifted), in record time.
I'm pretty sure one can have a up and running mail server while the "cloudformation" thingy will still be running :)
The emails sent from my $5 VPS arrives in Gmail's priority box :)
I suspect the "serverless" word was created due to the emotional appeal to a specific (majority) group that is strongly opinionated against having servers at all.
Reading from the README.md file:
There are two major limitations with SES:
For security reasons, AWS defaults to 200 emails sent per 24 hour period at a rate of 1 email/second. If you need to send more than that, you'll need to ask AWS to increase your limit.
By default, you can't send emails to unverified addresses. If you'd like to be able to send (as opposed to just receiving), you'll need to reach out to AWS to remove this limitation from your account.
I see zero benefit in having complete vendor lock-in, non-sense limitations, seriously, with a $5 VPS can send at least 300 emails per minute.My (opinionated) take on this if you are just starting a new business:
0. Lay your foundation on something that is battle tested and well supported.
Rent/buy a real computer (dedicated/root server), not cloud.
Use software that is already included in major/stable GNU/Linux distributions.
1. Build your stuff.
Get used to writing things.
Beware tech news. $ curl http://bofh.bjash.com/ -I
HTTP/1.1 200 OK
Content-Length: 22100
Content-Type: text/html
Last-Modified: Mon, 09 Sep 2019 18:36:39 GMT
Accept-Ranges: bytes
ETag: "916293843d67d51:0"
Server: Microsoft-IIS/10.0
X-Powered-By: ASP.NET
Date: Mon, 30 Dec 2019 18:53:47 GMTAnd that is ok.
Seems that you are really frustrated because you had a bad experience while working with a sysadmin and I don't think it is fair to despise people who do system administration just because of that.
This is toxic, and is _not_ ok.
Sysadmins are busy people, with their own reponsibilities, tasks, etc. They are always willing to help, assuming that you know how to communicate nicelly, tell about what you want to achieve, being a humble, honest human being.
Assuming that the sysadmin profession entails helping people all the time is plain wrong. Don't abuse.
Though, even if you ask for help several times about a specific subject is very likelly you will receive useful links, docs etc to get you "unblocked".
You still have to read and try to help yourself with the new piece of knowledge that you received.
_Demanding_ to help all the time is _not_ ok.
Peace!
Programming is a subset of skills within the sysadmin role.
Assuming that this is something like pgbouncer or pgpool that sit between the client and the database, and that you have a limit of connections with the database as well as the number of client connections you can keep, what value does this adds compared with those other (more mature, battle tested, included in major distros) projects?
1. "fix incorrect mayonese".
2. "fix incorrect lazagna"
and compare with:
1. "fix incorrect mayonnaise".
2. "fix incorrect lasagna"
When you treat configuration as flat files your configuration becomes a 1:1 mapping of the thing you have running.
I guess you should start with the first link, the one that says "About Debian". There you can know what Debian is about and align your expectations.
If you think it works for you, then go back to www.debian.org and do a ctrl+f and type "download", there is a big button in the top right corner. It is probably what you need (amd64, netinstall).
Search for "debian non-free iso" and you probably will find what you are looking for.
> ...nightmare maze of wrong links and secret knowledge.
Please, don't exaggerate.