The error is sent out by Varnish, but there's no way to know the reason by looking at the message. It could be a backend that's not responding or something else.
Go with Subversion, Git or some other VCS. It's simple and should provide enough automation.
Git doesn't support partial clones/checkouts, so I had to use Subversion instead. What a pity.
Yes, there are, but stay away from all the optimization flags. They bring more trouble than they're worth, so it's rare that people running FreeBSD will use them.
Some optimizations are already done (such as using -O2 or -O3), so the defaults should be fine.
If you really insist on using them...
Tried out Windows, Fedora, and Ubuntu before using FreeBSD. Someone introduced me to FreeBSD in my first year of high school, and I have been using it ever since.
Found a small problem on line 214:
rsync_options+=${rsync_opt_append}
The "+=" doesn't work for Bourne shell. This should fix it:
rsync_options="${rsync_options} ${rsync_opt_append}"
Take a look at Using Rsync and SSH.
Although it might be easier at first to use rsnapshot, some people prefer to write their own scripts since it provides more flexibility.
88SX6081 is listed in sys/dev/ata/chipsets/ata-marvell.c, so it should be supported. Try asking on freebsd-current@ and freebsd-stable@ and submit a PR.
I usually update ports as soon as an update comes out since I don't have many ports installed on my servers. Downtime is usually only a minute or two.
As for base, I only upgrade FreeBSD when a vulnerability affects me or when there is a new version (I use RELENG_X_X). The downtime is usually...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
