Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment: Re:Cannot reproduce your test case (Score 1) 445

by Eunuchswear (#49550039) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

That's not what I see on RHEL7

But it is exactly what I see on CentOS 7. How odd.

Type=oneshot

Where is this documented? I didn't see it in the man page for systemd, systemd.unit, systemctl, etc. or any other commands listed in the "SEE ALSO" sections of those commands.

man systemd.service

In man systemd I see:

The following unit types are available:

                1. Service units, which start and control daemons and the processes
                      they consist of. For details see systemd.service(5).

  [...]

SEE ALSO
              The systemd Homepage[9], systemd-system.conf(5), locale.conf(5),
              systemctl(1), journalctl(1), systemd-notify(1), daemon(7), sd-
              daemon(3), systemd.unit(5), systemd.special(5), pkg-config(1), kernel-
              command-line(7), bootup(7), systemd.directives(7)

And in systemd.directives there is:

Type=
                      systemd.mount(5), systemd.service(5)

Comment: Re:systemd rules!!! (Score 1) 445

by Eunuchswear (#49550013) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

"shit" does happen. What is interesting about the whole systemd thing is that there are a class of people, all posting AC, why lie about what happens.

I'd love to know why. I can understand that people don't like some software, but why would they flat out lie about what that software does?

How do I know these claims are lies? Because they are all posted AC, because nobody has ever claimed to have reported these defective behaviours as bugs, because I can't reproduce them even when using exactly the same environments and commands as the claimant.

Comment: Re: systemd rules!!! (Score 1) 445

by Eunuchswear (#49549993) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

I did try it, and reproduced the his results on Fedora 21.

That's very interesting, you're the first non-ac to report this.

Care to show me exactly what you did?

If you took the recipe given by the ac:

It is trivial to reproduce this serious problem with systemd. Pick any script in /usr/lib/systemd/*.service:

# append --broken to ExecStart line
vi /usr/lib/systemd/system/named.service
systemctl stop named
systemctl start named

Then maybe you missed the fact that systemd doesn't re-read unit files for existing services, you have to do a "systemctl reload" after stopping the service and before restarting it. (You should have got a message warning you of this, but many people seem to misunderstand the message).

Comment: Re: systemd, eh? (Score 1) 445

by Eunuchswear (#49549837) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

Bug report:

      * What led up to the situation?

I tried to talk to a troll

      * What exactly did you do (or not do) that was effective (or
          ineffective)?

I asked a question, hoping for an informative answer

      * What was the outcome of this action?

The troll gibbered at me

      * What outcome did you expect instead?

The same thing.

Oh, drat, it's not a bug, the troll is working as expected.

Comment: Re:systemd rules!!! (Score 0) 445

by Eunuchswear (#49548143) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

I can find the bug in an overly complex init script, yes. If they had a simple systemd unit there would be no bug to find.

(I found the bug in the init script in 10 minutes, the GP claims it took his crew of elite developers and Redhat support a whole day. Either he is an idiot or he is lying -- I suspect both).

"It's when they say 2 + 2 = 5 that I begin to argue." -- Eric Pepke

Working...