XPost: alt.os.linux.mageia   
   From: jdbeard@patriot.net   
      
   On 03/12/2013 03:05 PM, unruh wrote:   
   > On 2013-03-12, unruh  wrote:   
   >> On 2013-03-12, Bit Twister  wrote:   
   >>> On Tue, 12 Mar 2013 17:25:46 GMT, unruh wrote:   
   >>>> On 2013-03-12, Bit Twister  wrote:   
   >>>   
   >>>>> You better test and get use to a systemd only init process and   
   >>>>> journald commands to check/read the logs.   
   >>>>   
   >>>> Does that mean that the old init.d processes will not work at all on   
   >>>> this system?   
   >>>   
   >>> I do not like the wording of the question.   
   >>>   
   >>>>   How does one transfer over old init.d processes to systemd?   
   >>>   
   >>> I am going to substitute processes with scripts.   
   >>   
   >> Fine.   
   >>   
   >>>   
   >>> The majority of init scripts have been migrated as you can see from   
   >>> what is left to be converted:   
   >>   
   >> Is there any point to this waste of time-- ie the conversions?   
   >>   
   >>>   
   >>> $ ls -1 /etc/rc.d/rc3.d/S*   
   >>> /etc/rc.d/rc3.d/S09resolvconf   
   >>> /etc/rc.d/rc3.d/S10network   
   >>> /etc/rc.d/rc3.d/S13irqbalance   
   >>> /etc/rc.d/rc3.d/S13msec   
   >>> /etc/rc.d/rc3.d/S20vboxdrv   
   >>> /etc/rc.d/rc3.d/S35vboxautostart-service   
   >>> /etc/rc.d/rc3.d/S35vboxballoonctrl-service   
   >>> /etc/rc.d/rc3.d/S50network-up   
   >>> /etc/rc.d/rc3.d/S51mysqld   
   >>> /etc/rc.d/rc3.d/S80postfix   
   >>> /etc/rc.d/rc3.d/S95microcode_ctl   
   >>>   
   >>> If you have rolled your own scripts, just create a unit file which   
   >>> will call your script(s).   
   >>>   
   >>> Plenty of unit files found in /usr/lib/systemd/system/   
   >>>   
   >>> As an example, all the stuff I used to add to rc.local, I now have in   
   >>> local.rc. I then copied /usr/lib/systemd/system/rc-local.service   
   >>> to my local-rc.service file and changed it to the following:   
   >>   
   >> What is the difference between rc-local.service and local-rc.service?   
   >>   
   >>>   
   >>> $ cat local-rc.service   
   >>> [Unit]   
   >>> Description=/local/bin/local.rc   
   >>   
   >> What is local.rc?   
   >>   
   >>> After=network.target   
   >>>   
   >>> [Service]   
   >>> Type=forking   
   >>> ExecStart=/local/bin/local.rc start   
   >>> TimeoutSec=0   
   >>> RemainAfterExit=yes   
   >>> SysVStartPriority=99   
   >>>   
   >>> [Install]   
   >>> WantedBy=multi-user.target   
   >>   
   >> What does this mean?   
   >> Is there any description anywhere of what all of these options are and   
   >> mean?   
   >>   
   >> Sorry to sound grumpy, but it is annoying, after having spent 15 years   
   >> learing init.d to suddenly have to change for no good reason that I can   
   >> see, except to make things more obscure. I suppose that the next thing   
   >> is to make these files all compiled binary files as well, so they are   
   >> utterly unreadable and useless to the user. And then perhaps to put them   
   >> all into one humungous file.   
   >   
   > Ah, I see they have already gone down that road. All of the files in   
   > /lib/systemd/ ARE binary files, so that there is no way of finding out   
   > what the hell they do, except reading the source code. What fucking   
   > stupidity this is (excuse my language).   
      
   Except those in /lib/systemd/system that are ASCII.   
      
   >>> and copied it to /usr/lib/systemd/system/local-rc.service where   
   >>> systemd will run it after network.target has completed.   
   >>>   
   >> How does it know which runlevel to run it at?   
      
   Cheers!   
      
   jim b.   
      
   --   
   UNIX is not user unfriendly; it merely   
         expects users to be computer-friendly.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)