Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment How it went down (Score 1) 193

More likely:
Manager: "Hey, you promised a year ago that you could hit both NOx and MPG targets by Oct. 1. It's September already. How close are you to done?"
Engineers: "We promised what? You're sure? We said it would be a software fix? Really? OK, software guys- what's the hold up?"
Software engineers: "The guy who promised that left to join Facebook a year ago."
Manager: "Tough. Will you have the problem solved by Friday, or do I have to ask headquarters for another week?"
Software engineers: "This is a tough problem. I'm not sure it can even be done, but even if it can, it will take a year to do it right."
Manager: "I don't care about doing it right. Bash something together to make it pass the damn tests. Just do it."
Software: "It's really hard...
Manager: "OK, you have until Monday. Or you're all fired."
Software: "Uh, you said anything? As long as it makes the problem go away?"
Manager: "I'm giving you carte blanche. Don't worry about documentation, total quality, all that ISO s@#!t, I'll cover for you. Just make it pass the test."
Software: "Anything, huh? OK, we're on it."

Comment Re:I guess they realised... (Score 1) 79

No, there is not requirement to use PID files. That is simply a common way to implement a daemon. With sysvinit and sysvrc (or OpenRc), this kind of thing is an implementation detail that is out of scope.

Of course. Keeping track of running services is out of scope for a service management system. Genius.

It seems to me that the reason why pid files still exist is because sysv provides next to nothing, so people end up using the easiest, but about the worst approach available.

Patently incorrect, as I have used syslog to inspect startup crashes many times over the last *twenty years* I've been using UNIX. Maybe this has been a problem for other people, but I've never seen it. If your syslog is configured badly, that's an entirely separate problem.

Not startup. Crashes, as in segfaults. Those of course don't get logged since sysv doesn't monitor what it runs. Add the wonders of pid files to that and you get a service that sometimes needs to be fixed by hand to be restarted.

Also note that I'm talking about the init system, and not about individual services doing their own logging.

While I can't speak for all distributions (you seem to have had some history with poorly-configured environments), there is nothing wrong with using sleep based polling. The only reliable way to detect if a prerequisite service is ready is by directly polling the service. (e..g issue an HTTP GET to a web server) The timeout is to allow startup to proceed in case of an error, (so you don't end up bricked, unable to use your computer)

No, no polling. Just a plain "sleep 5" in a script that hopes that the service it depends on has time to properly get started in time. I sure hope no distribution ships this kind of crap anymore, but I seem to run into such hacks annoyingly often for some reason.

There is a reason most distributions stopped using super-servers like xinetd: on-demand startup isn't that useful. Start your service at boot. You can defer expensive tasks until the first requests, if you want, which is when you would pay that cost anyway in an "on demand" launch. Listen to on the port, block on accept(2) or select(2) or similar, and let the OS page you out to the swap partition.

Of course it's useful. Why should something like cups get started without a printer? Why should the user know to enable it once they get one? These days hardware changes at runtime, and things are expected to work when you plug in a printer or a bluetooth adapter, and not to complain or stop booting if some hardware turns out not to be there anymore.

Want to have some fun? On a systemd box, pretend you just installed some updates, and you need to restart a few daemons so they run the updated versions. Try restarting dbus (system, not user). (You might want to make sure any open files are saved first)

I get a slightly ugly message from systemctl, but other than that everything seems to be working fine. Restarted it a couple times just to be sure, checked that yep, the pid changes.

Also, you might want to actually read about UNIX before you make these kinds of accusations.

I speak from personal experience

Reading taoup is a good place to start.

Thanks, but I'm not religious. I prefer things that are convenient to those that are ideologically pure.

Comment Re:Figuring (Score 1) 166

It's probably not much of a factor. iOS apps are aggressively throttled in the background. Facebook plays all sorts of dirty tricks to keep running (apparently like trying to pretend it's an audio app, I've heard?) but otherwise, most apps happily accept the kill signal and take up no additional CPU time.

Comment Re:Battery Life (Score 1) 166

Really? My friend can't make it through half a day without running to charge her Galaxy S5, whereas I get 12 hours of actually tapping on my screen on my iPhone 6.

My anecdote is at least as good as yours.

The 6 and 8 hour values are through synthetic benchmarks that purposely stress the processor and display things on the screen non-stop. I've never gotten as little as 8 hours from my phone, even on a day where I all I do is play games and load webpages. Apple's devices generally get about 10 hours of usable battery, and that's exactly how it's been for the last 4 years.

They do it as a trade-off for phone thinness. I'd rather have a thin phone and a thin case than a bulky phone that lasts 2 hours--or even 10 hours--longer. If I change my mind, I can buy a case that has a battery built in to it. But if I start with a bulky phone, I can't make a thin phone out of it. That's the tradeoff I'm willing to make.

Comment Re:Bullshit ... (Score 4, Insightful) 193

No, the point (made many times already, try googling for once)

Oh go fuck yourself.

VW lied about how they achieved these numbers, and are claiming a couple of software engineers are the culprits.

So, yes, actual mechanical parts they never implemented and then lied about, and now they're looking for a scapegoat.

The people responsible for the engine design pretty much had to know this. Blaming it on software engineers is an outright lie.

They lied about how they did this, they lied about how they faked it, and they're lying about who is at fault. The only "clever design" was systematic fraud.

Comment Bullshit ... (Score 4, Insightful) 193

Aren't there actual mechanical parts of the engine which simply weren't even implemented and then this kludge was done in software?

You can't design this way of cheating without people who know the details of the engine signing off on it.

This is so much bullshit it isn't funny.

A software engineer could not have made the decision to leave off the components which were supposed to make clean diesel.

This is purely about finding a scapegoat.

Comment Pretty much screwed ... (Score 1) 25

He allegedly encouraged the hackers to use the credentials to âoego fuck some shit up.â

And, really, if that was his attitude, he gets no sympathy.

In terms of the definition of "computer fraud and abuse", that's pretty much it.

Of course, the problem is you could do a LOT of non-digital crimes and do a LOT less time, which makes me ask if these prison sentences are even sane.

Hell, you could probably intentionally run down someone with your car and do less prison time.

Comment Re:MOOC = Massive Open Online Course (Score 1) 86

Bah ... MOOCs are for cows, you're all cows ... MOOC cow ... MOOC ... cower before me and stuff.

Yay cows ... or whatever that cow thing is supposed to say. It's cows all the way down.

MOOC may be used a lot, but so are all other bullshit buzzwords ... Massively Online Ocelots and Cows or something.

It may surprise you that a lot of us don't give a crap about these buzzwords, and don't keep track.

Now moove along.

Comment Re:Define speeding (Score 1) 147

Really? You mean I can tell the officer I was doing 80 in a 50 zone because I was passing someone?

I'm pretty sure I've never heard of passing as an exemption to speed limits. I'm pretty sure they don't write traffic laws which says "you can't go faster than X ever, unless you're passing, then it's OK".

Are you sure it's actually "legal"? Or just something you heard once?

Comment Re:I guess they realised... (Score 4, Informative) 79

Care to point out a couple of those bugs?

Okay, sure.

  1. It does next to nothing. All the real functionality is in distribution specific scripts, which means you need to research and write a script for each distribution you want to support, each with its own particular features and idiosyncracies.
  2. Each script is a bunch of boilerplate that has to reimplement the same stuff. Often badly, especially when an init script has to be improvised.
  3. The functionality is inconsistent between services. Some can be restarted, some not. Some have a status command, some not.
  4. To check whether a service is running, it uses pid files. Pid files are horribly unreliable and prone to failing if a pid file happens to be left around, and something else happens to use the same pid.
  5. If you want start on demand, eg, something like xinetd, that's an entirely different system that's managed differently and separately.
  6. If you want a service to get automatically restarted, that's also done with an entirely different system like monit.
  7. It doesn't have useful logging. Processes can vanish into the ether without useful information in the logs because stderr may not be captured in some cases, and because init doesn't log service crashes.
  8. Service providing services are tricky. You may know the daemon has started, but you don't know it's now accepting requests. Yay for "sleep" hacks.
  9. Breaks horribly the moment something goes wrong. Network cable not plugged in? Well, if you boot like that nothing network related works, so you've got to log in and fix it by hand.

Comment Re:Idiots (Score 1) 297

Unfortunately, in the modern context "mentally infirm" is pretty much a design feature, and people feel they're entitled to believe any old irrational shit and that should be OK.

There's a tremendous amount of people who seem to wear their own self-created ignorance as some kind of badge of honor.

"Complete idiots" now probably covers a good portion of society these days ... and we seem to accept this as a fairly normal thing.

Your good nature will bring you unbounded happiness.