Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re: Curing meat into bacon (Score 1) 242

However, that is not the only means to curing it. It can be solely salt cured and hung to dry. That's how I prefer my bacon. (I lie, I also heavily pepper it.)

From what I understand, the smoke ring created when smoking a meat creates some level of nitrites/nitrates in the meat, but rather than being through the meat, it is just near the surface which implies fewer nitrates/nitrites. In either case, if I want to add a smoky flavor to the bacon, then I will lightly smoke it (smoke it at a very low temp for approx 4hrs) before I salt and hang it.

In the end, I end up with something much less salty than the store bought stuff. It leaves a less lingering taste in the mouth, and for some reason doesn't make me feel nearly as thirsty.

All of that work can be done in a small apartment with a patio. If you're good at bartering, it can definitely help your neighborhood relationships as well.

Comment Re:I'm not surprised. (Score 5, Informative) 917

Even so, in every bit of coaching that I have ever seen, there is a requirement of: request, rebuff, request again, escalate, unless the references are "to the reasonable person" offensive in the extreme.

That also seems to follow the legal doctrine on the matter. An advance is considered normal and human (if stupid, from a manager), the repeated advance in the face of clear rejection causes the condition to rise to harassment. This goes for passive things like, a mudflap girl coffee mug, inappropriate humor, etc.

I agree that the victim should escalate early and often for their own protection and documentation, but the HR person (if they were being honest) did the right thing. If we went around firing everyone for the first inappropriate thing they ever did the manpower churn itself would be a viable alternative power source.

I'm not a lawyer, advisor, or necessarily reasonable. I'm just old enough to see this go around multiple times, sometimes having negotiated successful resolutions... sometime having quit MY JOB because of the treatment of peer and the company's response.

Comment Re: Coming from an information security academic (Score 1) 88

Other folks here have provided insight and commentary that you likely have no clue as to what you are talking about, but who doesn't love a dogpile?

I have implemented MANY very large Splunk and ELK implementations. ELK will almost always ask for MORE hardware to get search performance. I agree that ELK scales out more quickly, but far less efficiently than Splunk does. If your sole criteria is search speed and you have unlimited hardware capacity then ELK is the way to go.

However, doing calculations on the logs, presenting the logs, transforming the data (geo IP lookups, changing the message so that it reads more easily), and doing multivariable comparison for either human or automated response is vastly superior in Splunk. In both the functions and toolkits available and the ability to front load a lot of your search work so that your performance is outstanding.

Cost wise... it's usually a wash. I have customers that have looked at the cost of installing and maintaining an ELK stack and replacing the lost features and ran away quickly. This is for >500GB/day infrastructures with a dedicated dev team of >3 people.

If your Splunk implementation is sucking wind that badly, then it is likely that whoever is paying for your implementation has expressed goals that are counter to your goals and thus you are ill served. If you are the payer, then you have done poorly at describing your desired outcome and approx 50% of the result is your fault.

Continuing on... You mention Flume and Solr. Solr, if you buy the production implementation (last time I looked) doesn't have a good flow control and message verification platform and is thus dependent on the messaging bus within Flume or the implementation of an outside message bus (Kafka, Redis). This results in another set of configurations to maintain, and a good place for logs to be lost in the ether. Flume itself is awesome, although the parsing recipes could use some work. If I were looking outside of Logstash/Beats (which is advisable as Logstash seems to still have some memory management issues) I would favor Fluent as the ingest process is less of a pain in the neck.

However, I've only done hundreds of implementations of log management infrastructures using logstash, ElasticSearch, Kibana, flume, kafka, redis, fluent, syslog-ng, and/or Splunk... so there are likely some options I haven't mentioned.

Slashdot Top Deals

How can you do 'New Math' problems with an 'Old Math' mind? -- Charles Schulz

Working...