[SOLVED] systemd + netatalk after update

Ask questions about Arch Linux ARM. Please search before making a new topic.

[SOLVED] systemd + netatalk after update

Postby robotron1971 » Tue Oct 23, 2012 6:14 pm

After a recent update, netatalk was up and running, but was throwing CNID errors upon connect.

Investigation showed that the CNID folder that was recently created was owned by root (created during the upgrade), and the 'netatalk' user couldn't write to it.

I changed permissions, and then went to restart netatalk like so

$this->bbcode_second_pass_code('', '/etc/rc.d/netatalk restart')

Only to find that there is no netatalk entry. Nor is there an avahi-daemon entry in the folder.

I took a look at the netatalk 3.0 package info in the AUR (which is what pacman seems to have installed http://aur.archlinux.org/packages.php?ID=10032 )

And find that this package is systemd-only

so, i try to run systemctrl to get a list of running applications/manage /restart them and I get this:

$this->bbcode_second_pass_code('', 'Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory
')

So I created the file, ran it again, and came up with this:

$this->bbcode_second_pass_code('', 'Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
')

But, i run 'ps' , and i find that netstat (and afpd) are running.


So i started to feel that perhaps i foolishly overlooked some update notes, and found a bunch of stuff in the main archlinux forum about the move to systemd, and thought "well, I'll just move things over to systemd"

I restarted, and still have the same issue.

One interesting thing about the docs that point to changing to systemd , is that they all refer to editing the bootloder to change your "init=" statement.

The thing is, on the dockstar, I am using uboot, and connot seem to find info re: changing the init value

I tried to recreate the rc.d files, and while teh file creation seems to work, starting and stopping fails


So, three questions:

1) Can someone help me with the systemd/D-BUS messages?

2) has anyone else successfully created rc.d style startup scripts for the new netatalk package?

3) for the record, how would i modify the uboot settings to use systemd in the init= value
Last edited by robotron1971 on Wed Oct 24, 2012 1:51 am, edited 1 time in total.
robotron1971
 
Posts: 11
Joined: Mon Jul 19, 2010 8:06 pm

Re: systemd + netatalk after update(dockstar) : confused!

Postby pepedog » Tue Oct 23, 2012 6:53 pm

You don't have to mess with uBoot.
Just follow mixed, follow the guide, if all is ok remove initscripts
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: systemd + netatalk after update(dockstar) : confused!

Postby robotron1971 » Wed Oct 24, 2012 1:43 am

$this->bbcode_second_pass_quote('pepedog', 'Y')ou don't have to mess with uBoot.
Just follow mixed, follow the guide, if all is ok remove initscripts


Hey Pepe,

That is what i thought, but the "mixed systemd/SysVinit/initscripts installation" section says "dd init=/usr/lib/systemd/systemd to the kernel parameters in your bootloader" and the "mixed systemd/initscripts installation" says "Follow the instructions for a mixed systemd/sysvinit/initscripts installation" ...i read that to mean "follow all of the above steps, and then here are some more"....

Was i wrong? do they just mean to install systemd ?

Thanks for taking the time to spell it out! I jsut don't want to break everything and start from scratch.
robotron1971
 
Posts: 11
Joined: Mon Jul 19, 2010 8:06 pm

Re: systemd + netatalk after update(dockstar) : confused!

Postby robotron1971 » Wed Oct 24, 2012 1:50 am

Ah, i read more closely: Once the systemd-sysvcompat
package is installed, the "init=" is no longer necessary.

Thanks Pepedog!
robotron1971
 
Posts: 11
Joined: Mon Jul 19, 2010 8:06 pm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 2 guests