Darrell, Tim,
Do you have artsd.service files for arts in any of your distros? We will probably need one to manage the daemon under systemd.
systemd is compatible with old school sysv scripts no?
On 26 January 2014 06:38, David C. Rankin drankinatty@suddenlinkmail.com wrote:
Darrell, Tim,
Do you have artsd.service files for arts in any of your distros? We will probably need one to manage the daemon under systemd.
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 01/26/2014 02:54 PM, Calvin Morrison wrote:
systemd is compatible with old school sysv scripts no?
Yes, but it looks sloppy to have /etc/rc.d/anything.... Nothing will turn the Arch devs noses up quicker. I got one for kdebase and a couple of others. Most of the tde apps will NOT need one since they are launched via .desktop files, but for the daemons and other things launched via starttrinity or xinit, we may need one for completeness.
I'm still working on what does/does NOT need the systemd service files. Basically, as a rule of thumb, if it was originally packaged with a sysvinit script in /etc/rc.d/foo then I think we provide a .service.
I really need a tutorial on what gets "one-shot"'ed, etc.. If you or anyone has a good link or reference for what the criteria of how service files are setup for different types of processes, I would welcome the help.
man systemd.unit does a pretty good job, but it is written with man page mentality - great for a reference for experienced unit file creators. Maybe not so good for learning it. There are some useful freedesktop links at the bottom that help.
On 01/26/2014 06:18 PM, David C. Rankin wrote:
On 01/26/2014 02:54 PM, Calvin Morrison wrote:
systemd is compatible with old school sysv scripts no?
Yes, but it looks sloppy to have /etc/rc.d/anything.... Nothing will turn the Arch devs noses up quicker. I got one for kdebase and a couple of others. Most of the tde apps will NOT need one since they are launched via .desktop files, but for the daemons and other things launched via starttrinity or xinit, we may need one for completeness.
I'm still working on what does/does NOT need the systemd service files. Basically, as a rule of thumb, if it was originally packaged with a sysvinit script in /etc/rc.d/foo then I think we provide a .service.
I really need a tutorial on what gets "one-shot"'ed, etc.. If you or anyone has a good link or reference for what the criteria of how service files are setup for different types of processes, I would welcome the help.
man systemd.unit does a pretty good job, but it is written with man page mentality - great for a reference for experienced unit file creators. Maybe not so good for learning it. There are some useful freedesktop links at the bottom that help.
For packagers with similar questions:
http://0pointer.de/blog/projects/systemd-for-admins-3.html
Le 26/01/2014 12:38, David C. Rankin a écrit :
Darrell, Tim,
Do you have artsd.service files for arts in any of your distros? We will probably need one to manage the daemon under systemd.
artsd is a not a system service, it's run as a background process by the user during the TDE session opening. So there is no need to use systemd for this one.
Francois
On 01/27/2014 12:43 PM, François Andriot wrote:
artsd is a not a system service, it's run as a background process by the user during the TDE session opening. So there is no need to use systemd for this one.
Francois
Thanks Francios,
That is what drives me nuts right now. Determining what does/doesn't need service files. I have been checking what kde has done and adding those found (tdebase, etc..) I see the tdebase requirement being the graphical-target.wants... requirement, but beyond that I just have to check on each daemon acting package...