3

From what I understand, the file /etc/init.d/boot.local is a perfectly legit place to sprinkle a few extra commands you would like to be run when SLES 11 starts up. However, when our organization recently upgraded to SP2, this file was completely overwritten on our boxes.

Were my initial assumptions wrong? According to documentation (and the comments in the file itself) this file should be OK. But I'm not about to be burned a second time.... so where should I place these commands instead?

Note that I wish for these commands to be run before rc services are start. Therefore the boot.local file was perfect for our needs.

Thanks!!

Alfred Fazio
  • 131

1 Answers1

1

From my limited experience with SLES you put your local customizations in the right place.

That being said, you did the Wrong Thing when you upgraded without first backing up your local settings -- the fact that the update also did a Wrong Thing by trashing that file on you notwithstanding, if you want to avoid being burned make sure you don your asbestos undergarments (and back up your local customizations) before turning an upgrade process loose).

Service Packs (distribution upgrades, major release upgrades, etc.) are especially likely to break things on you, and deserve this level of extra caution...

voretaq7
  • 80,749