Understanding SLES boot order file relationships

Hi all, In SLES in general, and SLES 11.x specifically, what is the order that boot files are processed. I’m thinking that it’s…

/etc/init.d files
then any /etc/profile and /etc/profile.local is processed
then the individual’s .bashrc and .bashrc.local is processed last.

Is this correct or out of order? And are there any other files I’m missing?

There is also the user .profile, as well as other .files eg .xinputrc .gtkrc etc, then of course anything set in the autostart directory.

The init files as processed in order of runlevel and # order set in the init file which can be seen down in the respective /etc/rc.d determined vi Snn for start order and Knn for shutdown order.

@jgosney - in addition to what malcolmlewis said, check man bash - look for the chapter “INVOCATION”. It’s explained there quite well how the login and nologin shells are set up.
But init.d files are first, yes. The rest depends on your configuration, e.g. you can use other shells than bash.

Hi jgosney,

generally speaking, on boot the entries in /etc/inittab are evaluated and the corresponding commands are invoked. You ought to find references to “/etc/init.d/rc” there, which is the wrapper to the invokation of the files in /etc/init.d.

/etc/profile is invoked on login of a user - which may be never on a server system. From there, /etc/profile.local is triggered and all appropriate scripts under /etc/profile.d. Since you asked for SuSE… there’s “/etc/SuSEconfig/profile” which is invoked from within /etc/profile, too… If your shell is a bash, then don’t forget /etc/bash.bashrc (ksh uses /etc/ksh.kshrc) and of course the user’s local scripts, depending on your $SHELL.

With regards,