You are not logged in.
Hi all,
After the latest update I decided to jump to systemd completely, and have few questions.
- I used a static IP address set-up within rc.cong previously and wish to carry on, but the wiki regarding the network and systemd isn't very clear - could anyone point me to the right information?
- I have removed all my daemon from rc.conf at the exception of "xinetd" simply because I cannot find the name of the service to be enable.
- I am running squid on the computer and after checking the booting time it seems to take forever - is there a way to load service in the background like "@" previously or checking which order those service are starting (I have the feeling squid is trying to load before the network has started)
- Is there a way to use systemd to start application at boot time, like pyLoad (download manager)?
Looking forward for your replies,
Regards,
Offline
I won't be able to comment on everything, but here are my 2¢:
I used a static IP address set-up within rc.cong previously and wish to carry on, but the wiki regarding the network and systemd isn't very clear - could anyone point me to the right information?
If I recall correctly, networking in rc.conf is deprecated. You should switch to netcfg.
I have removed all my daemon from rc.conf at the exception of "xinetd" simply because I cannot find the name of the service to be enable.
What daemons did you have running before? Also, a "pacman -Ql <package> | grep service$" should list all service files belonging to a package. A common gotcha: There's not explicit dbus service file, dbus is at the heart of systemd and gets started automatically.
I am running squid on the computer and after checking the booting time it seems to take forever - is there a way to load service in the background like "@" previously or checking which order those service are starting (I have the feeling squid is trying to load before the network has started)
Systemd is, by default, "aggressively parallelized". The service file shipped with squid starts as soon as the network is available (due to the line "After=network.target"). You might want to read up on service files and targets (man systemd.service/systemd.unit/systemd.target) if you want to customize that.
Is there a way to use systemd to start application at boot time, like pyLoad (download manager)?
If you want to run pyLoad as its own user, just enable the service file shipped with it:
# systemctl enable pyload.serviceIf you want it to run at the start of your own user session, I'm afraid you'll have to wait a while—systemd for the user session is not yet ready for prime time.
Last edited by Runiq (2012-11-02 15:36:43)
Offline
- I have removed all my daemon from rc.conf at the exception of "xinetd" simply because I cannot find the name of the service to be enable.
Looking at the package file list here, it looks like the name of the service file is .... xinetd.service.
Seriously??
Last edited by Scimmia (2012-11-02 13:42:18)
Offline
sweetthdevil wrote:- I have removed all my daemon from rc.conf at the exception of "xinetd" simply because I cannot find the name of the service to be enable.
Looking at the package file list here, it looks like the name of the service file is .... xinetd.service.
Seriously??
Great thank you, never thought at looking there.
@Runiq Many thanks for your answer I am looking at them now.
Offline
I used a static IP address set-up within rc.cong previously and wish to carry on, but the wiki regarding the network and systemd isn't very clear - could anyone point me to the right information?
You can write yourself a network.service to set this up, there's an example on the wiki. Then simply enable the service and you're done.
Offline
Still haven't had the time to look more into the network, but pyload.service doesn't work properly. I follow the wiki page.
See below the terminal output of "sudo journalctl -n"
-- Logs begin at Wed, 2012-10-31 14:34:08 GMT, end at Thu, 2012-11-01 10:21:17 GMT. --
Nov 03 10:23:39 linuxbox systemd[1]: Unit pyload.service entered failed state
Nov 03 10:23:39 linuxbox sudo[2924]: pam_unix(sudo:session): session closed for user root
Nov 03 10:23:52 linuxbox sudo[3001]: sweetth : TTY=pts/1 ; PWD=/home/sweetth ; USER=root ; COMMAND=/usr/bin/systemctl status pyload.service
Nov 03 10:23:52 linuxbox sudo[3001]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)
Nov 03 10:23:52 linuxbox sudo[3001]: pam_unix(sudo:session): session closed for user root
Nov 03 10:24:01 linuxbox sudo[3008]: sweetth : TTY=pts/1 ; PWD=/home/sweetth ; USER=root ; COMMAND=/usr/bin/systemctl status pyload.service
Nov 03 10:24:01 linuxbox sudo[3008]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)
Nov 03 10:24:01 linuxbox sudo[3008]: pam_unix(sudo:session): session closed for user root
Nov 03 10:25:03 linuxbox sudo[3041]: sweetth : TTY=pts/1 ; PWD=/home/sweetth ; USER=root ; COMMAND=/usr/bin/journalctl -n
Nov 03 10:25:03 linuxbox sudo[3041]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)And the pyload.service file:
[Unit]
Description=Downloadtool for One-Click-Hoster written in python.
After=network.target
[Service]
Type=forking
PIDFile=/run/pyload/pyload.pid
ExecStart=/usr/bin/pyLoadCore --daemon
KillSignal=SIGQUIT
User=sweetth
[Install]
WantedBy=multi-user.targetLast edited by sweetthdevil (2012-11-03 10:28:19)
Offline