And you can start it in command line ?
(systemctl start tor.service)

Severity: normal => minor

This command does not start tor ! 

When I wore Mageia 1 I configured tor by drakxservices. Start in boot. Start or stop TOR.

>This command does not start tor ! 
that is the output then ?

Keywords: (none) => NEEDINFO

[root@ervamate chimarrao]# systemctl start tor.service
[root@ervamate chimarrao]# 

NULL output and I went on ksysguar tor is not running!

Developers have adopted Systemd being that he still is not fully integrated into Mageia and tools MCC. I ask then and now?

here it's a tor bug (or in the service file provide by fedora), see the same bug on redhat https://bugzilla.redhat.com/show_bug.cgi?id=744005

Keywords: NEEDINFO => UPSTREAM
See Also: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=744005
Summary: TOR disappeared from the list of services in drakxservices => tor service does'nt start ( was tor disappear in drakxservice)

Honestly don't see advantages in having replaced sysvinit by systemd seen several problems, bugs, so the Alt + SysRq: REISUB does not work with it.

Can I safely replace sysvinit by systemd in Mageia 2?

Now that I went back to sysvinit-legacy everything works on drakxservice and I
can configure the services that will go up on boot.

Summary: tor service does'nt start ( was tor disappear in drakxservice) => systemd bug: tor service does'nt start ( was tor disappear in drakxservice)

This is just a bug in the systemd unit in the tor package.

Please do not use the bug tracker as a system for discussing various systemd vs. sysvinit systems. sysvinit is much less tested than systemd on MGA2 and is thus likely to have more bugs.

That's not to say there are not problems in various packages, including tor which is the case here. And for the record, Alt+SysRq works fine under systemd as it did under sysvinit.

I'll take a look at the tor issue specifically.

Keywords: UPSTREAM => Triaged
CC: (none) => mageia
Summary: systemd bug: tor service does'nt start ( was tor disappear in drakxservice) => tor service doesn't start under systemd
Source RPM: systemd-44-13.mga2.src.rpm => tor-0.2.2.35-5.mga2

See more details about REISUB in systemd here and test and see the loop (bug) with X (DM):

https://bugs.mageia.org/show_bug.cgi?id=6843

(In reply to comment #9)
> See more details about REISUB in systemd here and test and see the loop (bug)
> with X (DM):
> 
> https://bugs.mageia.org/show_bug.cgi?id=6843

Umm, that's *this* bug.  

And while I have seen problems with systemd (including this one), I verify that systemd has no effect on Alt SysRq RSEIUB.  There have been system freeze bugs recently where lockups don't respond to the magic keys, but they have nothing to do with systemd.

CC: (none) => ftg

I've fixed the systemd unit in the tor package and submitted it to core/updates_testing for mga2.

Please test and provide feedback such that we can issue an official update.

Below correct link to REISUB broken with SystemD in Mageia 2:

https://bugs.mageia.org/show_bug.cgi?id=6842

Reinstalled again systemd as default. Updated TOR by media core/updates_testing for mga2. TOR continues not listed in drakxservices. Image below:
http://img713.imageshack.us/img713/5402/tory.png

OK, so there are two problems here! The first is that the tor systemd unit was completely wrong (blind copy+paste it seems) which is now fixed. This means the tor service can be started and stopped happily (systemctl start tor.service).

However there is still a problem with drakxservices not showing disabled units (which tor is by default).

One way to make tor show up in drakxservices is to run "systemctl enable tor.service". This will then allow it to be reported properly.

So, problem 1 is now fixed. problem 2 is outstanding although with a work around. I'll ensure I go and patch drakxservices code to cope with this and get an update ready.


FYI, the problem is just that drakxservices internally uses "systemctl list-units --all" to list all the available services. Sadly this does not show disabled services. So I will have to augment this with "systemctl list-unit-files" output. There is a call to make this behaviour different: https://bugzilla.redhat.com/show_bug.cgi?id=748512 Anyway I can easily work around this and will do so shortly.

OK, so I've submitted a new build of tor to fix a bug in my bugfix :) Please update to that.

Also I've just submitted a new build of drakxtools which should address the problem of drakxservices not listing disabled (but enablable) services.

Please update when it hits your mirror. I think this should address both the tor-specific problem and the issue of drakxservices not listing some services that it should have.

Problem 1: I tested the command and it worked:

# systemctl enable tor.service
ln -s '/lib/systemd/system/tor.service' '/etc/systemd/system/multi-user.target.wants/tor.service'
# systemctl start tor.service
# systemctl stop tor.service
# systemctl disable tor.service
rm '/etc/systemd/system/multi-user.target.wants/tor.service'

Problem 2: So this is the reason because with sysvinit shows services that does not show with systemd. I wait then release the fix.

Already updated TOR for 0.2.2.35-5.2.mga2
Not found update for drakxtools, drakxtools-backend and drakxtools-curses :-(
After a few hours I will try again!

Problem 2: I updated drakxtools-14.21-1.1.mga2 too. Many services that do not appear in drakxsevices now appears. Is very good now be integrated systemd with drakxservices and work.

Thank you for your personal efforts and by making increasingly mageia best!!!

Colin, what's the status of this update candidate?

SRPMs:
drakxtools-14.21-1.1.mga2
tor-0.2.2.35-5.2.mga2

In my Mageia 2 x86_64 is working perfectly!

I've issued an official update request for tor now: bug #7250.

As for drakxtools, myself and TV discussed this the other day. It think he'll be pushing an update, but I'll double check with him about it.

drakxtools update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0188

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED