Hi DongInn,

OSCAR::OCA::OS_Settings + OSCAR::SystemServices + OSCAR::SystemServicesDefs are 
handling all distro specific stuffs.

Trying blindly many methods leads to difficulties when trying to handle errors. 
More over, it means that all effort to provide an easy to use interface to 
service management is void if we still need if statements in the code to handle 
those kind of stuffs.

But don't worry:
I've understood all the possible issues and I'll fix this in either 2 ways:
1/ Handle xinetd compatibility in systemd enabled distros) => bonus: code in 
OSCAR dealing winth xinetd can be replaced with a simple SystemServices 
function, and SuSE specificity will vanish. (the code would hide if the service 
is managed thru init.d scripts or thru xinetd just like systemd does with 
daemons or sockets services).
2/ Fix atftp package (which so far is the only package having this issue. More 
over, this package is a daemon on SuSE and a xinetd service on other distros. 
this lead to multiple lines of code to manage it instead of 2 (one for start 
and one for enable). even worse, if atftp is replaced with another tftp daemon, 
the code may be broken.

Aside that, the good news is that I'm able to finish step 6 without errors on 
FC-17.
This means that most of core code is fixed by now.

Now I'll need to fix opkg scripts. (and Database.pm which has hardcoded 
postgress paths (not used though so not a priority).

Then I'll grep init.d, chkconfig, service in oscar sources and check if it 
needs to be fixed as well.
Still work to do, but the code is easier to read by now and will be easier to 
maintain IMHO.

Best Regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DM2I/DIR
________________________________
De : DongInn Kim [di...@cs.indiana.edu]
Date d'envoi : lundi 4 novembre 2013 20:02
À : Devel OSCAR
Objet : Re: [Oscar-devel] RE : [PROVENANCE INTERNET] native command to enable 
xinetd service on systemdsystem?

Hi Olivier,

Is there any problem with using the legacy upstart/chkconfig/xinetd on OSCAR?
Why don’t we use any of them which is applicable to the supported distros?
If one fails to find/run/config the startup program, another one is tried and 
another one until we run out of options in the script.

This way, we may keep supporting the backward compatibility and safely support 
many distros.

Regards,

--
- DongInn

On Nov 4, 2013, at 1:43 PM, LAHAYE Olivier 
<olivier.lah...@cea.fr<mailto:olivier.lah...@cea.fr>> wrote:


After searching for the info, the answer is that:

systemd "socket activation" is similar to xinetd. Not all services written to 
work with xinetd will work unmodified though.
OSCAR provides the atftp-server package. I'll give a look at it and see what 
can be done. If I can avoid xinetd service management in systemd compatibility 
mode, that would be fine.
So far, only tftp service is hitting this problem in oscar.

Source:
https://fedoraproject.org/wiki/Packaging:Systemd?rd=Packaging:Guidelines:Systemd

Regards,

--
   Olivier LAHAYE
   CEA DRT/LIST/DM2I/DIR
________________________________
De : LAHAYE Olivier
Date d'envoi : lundi 4 novembre 2013 19:29
À : oscar-devel@lists.sourceforge.net<mailto:oscar-devel@lists.sourceforge.net>
Objet : [PROVENANCE INTERNET] [Oscar-devel] native command to enable xinetd 
service on systemdsystem?


Hi

Does anybody know the native command in systemd enabled distro to enable a 
xinetd service?

In other words, what is the native command on systemd enabled distro to do:
chkconfig tftpd on
(result is that it sets disabled = no in /etc/xinetd.d/tftp file) and reloads 
xinetd service).

I'm working on setup_pxe migration (lots of work BTW), and I hit this 
problem.....
chkconfig is a compatibility command and will be dropped in the future.

Or maybe xinetd is obsoleted by systemd and thus, it's here for not yet 
migrated services as a compatibility service? (thus that would mean that 
searching for a native command is a non-sense?)

Thanks for any input.

Regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DM2I/DIR
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net<mailto:Oscar-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to