F15: most services sysvinit only?
Reindl Harald
h.reindl at thelounge.net
Wed Jun 15 23:51:13 UTC 2011
Am 15.06.2011 08:55, schrieb Tomasz Torcz:
> That's because maintainers largely ignored systemd
> integration furing F14 and F15 devel cycles. See bugs linked
> from: https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability
> There are few maintainers and upstream who responded quickly, though.
ugly!
maybe because they had the same problems as i now trying get a service for dbmail-imapd
running, sometimes it starts and most times not, the start-commadn says NOTHING,
starting with "service"-command is braindeaded and says always OK
i was really happy after getting a perl-daemon running with a .service-file
at the first attempt but some mintes later the smile was blown away
maybe because i have no idea what the two follwoing lines from the
sysv-script are doing nor how to get them in the .service-file but
on the other hand if i fire the binary as root it starts, drops
privileges and starts its childs - with systemd only sometimes
DBLIBDIR=/usr/lib/dbmail
export LD_LIBRARY_PATH=$DBLIBDIR:$LD_LIBRARY_PATH
and this state is ready to replace things worked 365/7/24
i fear not and it is killing my holidays
[root at testserver:~]$ service dbmail-imapd start
Starting dbmail-imapd (via systemctl): [ OK ]
_________________________
who did this?
why is here "systemctl" called what is NOT working?
[root at testserver:~]$ /etc/init.d/dbmail-imapd start
Starting dbmail-imapd (via systemctl): [ OK ]
_________________________
[root at testserver:/lib/systemd/system]$ cat dbmail-imapd.service
[Unit]
Description=DBMail IMAP Server
After=syslog.target mysqld.service local-fs.target network.target
[Service]
Type=forking
PIDFile=/var/run/dbmail-imapd.pid
ExecStart=/usr/sbin/dbmail-imapd
[Install]
WantedBy=multi-user.target
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: inactive (dead) since Thu, 16 Jun 2011 01:32:05 +0200; 6s ago
Process: 3262 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3263 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/dbmail-imapd.service
[root at testserver:/lib/systemd/system]$ systemctl start dbmail-imapd.service
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: active (running) since Thu, 16 Jun 2011 01:32:19 +0200; 2s ago
Process: 3273 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3275 (dbmail-imapd)
CGroup: name=systemd:/system/dbmail-imapd.service
├ 3275 /usr/sbin/dbmail-imapd
├ 3276 /usr/sbin/dbmail-imapd
└ 3278 /usr/sbin/dbmail-imapd
[root at testserver:/lib/systemd/system]$ systemctl stop dbmail-imapd.service
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: inactive (dead) since Thu, 16 Jun 2011 01:32:53 +0200; 1s ago
Process: 3273 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3275 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/dbmail-imapd.service
[root at testserver:/lib/systemd/system]$ systemctl start dbmail-imapd.service
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: deactivating (stop-sigterm) since Thu, 16 Jun 2011 01:33:01 +0200; 1s ago
Process: 3287 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3288 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/dbmail-imapd.service
├ 3289 /usr/sbin/dbmail-imapd
├ 3290 /usr/sbin/dbmail-imapd
└ 3292 /usr/sbin/dbmail-imapd
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: deactivating (stop-sigterm) since Thu, 16 Jun 2011 01:33:01 +0200; 2s ago
Process: 3287 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3288 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/dbmail-imapd.service
├ 3289 /usr/sbin/dbmail-imapd
├ 3290 /usr/sbin/dbmail-imapd
└ 3292 /usr/sbin/dbmail-imapd
[root at testserver:/lib/systemd/system]$ systemctl status dbmail-imapd.service
dbmail-imapd.service - DBMail IMAP Server
Loaded: loaded (/lib/systemd/system/dbmail-imapd.service)
Active: deactivating (stop-sigterm) since Thu, 16 Jun 2011 01:33:01 +0200; 3s ago
Process: 3287 ExecStart=/usr/sbin/dbmail-imapd (code=exited, status=0/SUCCESS)
Main PID: 3288 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/dbmail-imapd.service
├ 3289 /usr/sbin/dbmail-imapd
├ 3290 /usr/sbin/dbmail-imapd
└ 3292 /usr/sbin/dbmail-imapd
>> what is a little bit confusing is how to find out
>> what is enabled in which order, how to change and that
>> "chkconfig | grep on" lists only a subset of services
>
> There's no “order” per se on systemd. Services are started
> as they're needed.
but why in the world it ignores totally the start-order of existing
sysv-init-services resulting in a perl-policyd which needs mysql
fails to start?
>> "systemctl" gives ahughe list mixed mounted disks
>> and servcices and compared with a stripped down
>> F14 there are running much more stuff with a hughe
>> longer boot process :-(
>
> try “systemctl -t service”
does even not show the dbmai-servcies (dbmail-lmtpd, dbmail-imapd, dbmail-timsieved)
if they are failed/terminated by systemd - not a trustable output!
>> conclusion: i am really missing anything making "chkconfig" able display
>> all services and only them as followed, and yes this is really enough for
>> a stripped down fileserver as vmware-guest
>>
>> [root at fileserver:~]$ chkconfig | grep Ein
>> auditd 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> crond 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> lvm2-monitor 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> messagebus 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> netatalk 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> network 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> postfix 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> rsyslog 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> smb 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> sshd 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> udev-post 0:Aus 1:Ein 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>> vmtoolsd 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
>>
>
> Something like “systemctl show -p Wants default.target”?
is a little bit crippled against "chkconfig"
this is not all - where is mysqld?
why one line?
[root at testserver:/lib/systemd/system]$ systemctl show -p Wants default.target
Wants=systemd-update-utmp-runlevel.service dbmail-imapd.service httpd.service remote-fs.target dbmail-lmtpd.service
rsyslog.service dov
(END)
normally i would expect that things like "chkconfig" are shwoing all servcies
and preprade for the state of F15 - but there is nothing to get a trsutable information
what the system will start at next boot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20110616/41d36015/attachment.bin
More information about the devel
mailing list