gmazza
Caddy is written in Go, and make use of native fibers/green threads/goroutines.
Big network gear vendors that ship to ISPs have adopted early forms of AQM (both RED [3] and proprietary algorithms) quite a while ago - they had to:
(a) backbone routers have much smaller buffer-to-bandwidth ratio (compared to a PC or even home router), so endless buffering is not an option;
(b) buffer tail drops (i.e. what drop keyword does when added to tc filters/disciplines) interact really poorly with TCP bandwidth control algorithms, and rather badly with RTP streams, too (so drop is not an option either - it ruins user's connections; and
(c) ISPs and carriers would typically run links (on average) much closer to saturation than your typical home router, so situation where router has to make buffer/drop decision is much, much more frequent.
[1] My point above was that you don't really want to drop packets on the receiver side, after that packet already traversed expensive part of the network.
Yep. TC's default is to policy outgoing traffic, which in OP's example is a bunch of TCP ACKs essentially. Instead, they should be using ingress keyword, something like described here:
http://blog.stevedoria.net/20050906/ingress-policing-with-li...
Caveat emptor: ingress rate-limiting is hard. Long story short, it all boils down to what you do with non-confirming packets: There are two alternatives, and both are rather sub-optimal. You can either buffer/delay packets in kernel space (default, which leads to bufferbload and memory waste), or drop (which author linked above opted for, which leads to excessive retransmits and bandwidth waste).
# htb
tc qdisc add dev eth0 handle 1: root htb default 11
tc class add dev eth0 parent 1: classid 1:1 htb rate 1kbps
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 1kbps
# tbf
tc qdisc add dev eth0 root tbf rate 1kbit latency 42ms burst 2k
[1] i.e. stuff like "I would like to have tcp/80 limited to 10 mbit/s, tcp/443 limited to 15 mbit/s, while sum of above should never exceed 20mbit/s, and tcp/80 should get priority when competing for that shared 20mbit/s"
EDIT: changed to "burst 2k". Having burst lower than interface MTU will delay large packets essentially forever.
From example code attached to the original article (Linux only):
int outstanding;
ioctl(fd, SIOCOUTQ, &outstanding);If both you and your correspondents do use 3rd party IM client ([1], [2], etc), then just run OTR2 or OMEMO on top of the protocol, and let google store whatever it pleases - it's not going to be much use for them.
[2] http://www.theverge.com/2016/1/16/10780876/microsoft-windows...
I am attempting to install ubuntu 16.04 on my yoga 900.
The bios can see the 512 gb samsung hard drive and so can Windows.
The ubuntu installer can not see it at all.
I have the same issue with the 900S model.
I have tried the newest kernel 4.6 but linux doesn't
even list the pci express device in lspci.
[1] https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK...
Both are somewhat dated examples, that is pre-HTML5.
- Cheap cards would start corrupting right in the middle of first "apt-get update && apt-get upgrade";
- SanDisk Extreme Pro 16GB fared much better, but still we had several failures after half-a-year;
- Failure mode in both cases - corruption in superblocks and inodes, journal doesn't help much when recovering (we use ext4).
As a result, we settled on splitting each card into two root partitions - active and standby. To upgrade, overwrite standby one with dd, switch active/standby by editing /boot/cmdline.txt, and reboot.
When used as a generic storage with a complex write/delete/overwrite pattern, most card would start corrupting data fairly quickly.
- cache invalidation: check (root cause of the actual bug);
- naming things: check (terrible name for an article, as others already pointed out).
https://www.coreboot.org/pipermail/coreboot/attachments/2016...
If this will turn out to be something that could be reliably disabled on other laptops, this is going to be huge.
$ yum install bash-completion
Error: This command has to be run under the root user.
$ sudo <Alt-.>
$ sudo bash-completion > The press release was issued, I think, sort of as if it
> came from some sort of independent or cross-vendor project,
> and there’s the snapcraft.io site to back up that impression,
> but every Snappy committer is a Canonical employee
Obviously this is tightly locked down with cgroups.
[1] http://0pointer.de/blog/projects/socket-activated-containers...
[2] https://developer.atlassian.com/blog/2015/03/docker-systemd-...
VPS (virtual private servers) were available (and largely ignored) for quite a while before 2006, when AWS came along with the catchy word "cloud". This single word changed everything. Same technology all of the sudden became cool, and everybody started using it.
Maybe now it is the turn of PaaS [1] - call it "serverless" and folks finally start seeing all the benefits (true scalability, efficient resource utilization, timely and painless software upgrades, et c.)?
And <textarea> doesn't auto-complete regardless of explicit options.
If local admin is incapable of configuring user accounts, how are websites supposed to figure out who is who, and which browser is on shared computer?
After all, if managing user accounts is too hard for said admin (or we are talking about a shared PC in a library, which doesn't have user accounts as a matter of principle) - just make browser always start in private/incognito mode on shared computer. It is as easy as adding command-line argument "--private-window" for firefox or "--temp-profile" for chrome. That's it. Window closed - autocomplete gone. Problem solved.
onpaste="return false;"Not at all. Complete brand-name HDMI connector assembly costs 29 cents in 10K quantity. [1]
[1] http://www.mouser.com/ProductDetail/Amphenol-FCI/10029449-11...
http://www.lanazione.it/firenze/voragine-lungarno-torrigiani...