On Tue, Oct 11, 2011 at 1:27 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > > > Didn't do much research around this lately. > > Today I revived my SSD (we'll see) and therefore fell over systemd when > I edited grub.conf > > Where would/should I put stuff from /etc/local.d/ with systemd? > > I have some commands there setting parameters for ssd-usage and those > would be skipped (not executed) with systemd.
Those command are on a script, right? Lets say the script is called ssd-thingies; you put this on /etc/systemd/system/ssd-thingies.service: ---------------------------------------------- [Unit] Description=SSD thingies After=basic.target [Service] Type=oneshot ExecStart=/my/path/to/ssd-thingies [Install] WantedBy=multi-user.target ----------------------------------------------- Then you run: systemctl daemon-reload systemctl enable ssd-thingies.service Next time you reboot, the service will be called after the basic.target has been completed. You can look at the status of the script afterwards with systemctl status ssd-thingies.service If everything went OK, it should have a line like this: Process: 1234 ExecStart=/my/path/to/ssd-thingies (code=exited, status=0/SUCCESS) Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
