tc-config suggestion for syncronous startup scripts.

[gerald_clark]

tc-config runs bootlocal.sh detached.
This has lead to some confusion for people adding items to bootlocal.sh.

My suggestion is that tc-config instead run bootsync.sh in the forground.
The distributed bootsync.sh simply runs "bootlocal.sh &'.
This would allow users to add routines that must complete before login to bootsync.sh either before or after the
launching of bootlocal.sh.

Bootlocal.sh runs exactly as it has in the past.

[^thehatsrule^]

Are there scenarios that would require this?

[maro]

I guess this thread could be seen as an example why the suggestion makes sense (at least to myself).

Whilst there are probably ways around it in most cases I'd like to support the proposal. I see it as beneficial to have the ability to for the user to create (system-wide) syncronous and asyncronous startup events.

[curaga]

Any sync events can be put in .profile, .xsession?
Or root's .profile, launched only once.

[maro]

Hmm, in my view there is a difference between the original proposal and using an amemdment to any of the .profile or .xsession files: It is quite reasonable to assume that a user starts the X-server more than once, or (especially with 'multivt' now an option) a user does login more than once. In this case the events would get executed again, which might not be the intension of the user.

The way I understand it '/opt/bootsync.sh' and '/opt/bootlocal.sh' would be only run as part of the boot process. Which is different from the other options mentioned above.

[roberts]

Good discussion. OK. I will implement in next 3.1rc.