Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow setting post message from easyconfig file #542

Closed
boegel opened this issue Mar 18, 2013 · 5 comments · Fixed by #4145
Closed

allow setting post message from easyconfig file #542

boegel opened this issue Mar 18, 2013 · 5 comments · Fixed by #4145

Comments

@boegel
Copy link
Member

boegel commented Mar 18, 2013

In some cases, it would be interesting to allow setting the post message that is printed at the end of the installation process in the easyconfig file, e.g. for issuing warnings in case like bbcp which requires certain ports to be open for it to work properly.

The easyblock module already supports this via the self.postmsg class variable.

@boegel boegel modified the milestone: v1.X Jun 24, 2015
@boegel boegel modified the milestone: 3.x May 2, 2017
@Falkor
Copy link

Falkor commented Jun 22, 2017

+1 :) Have the case for LikWid where a setuid procedure is required for the daemon.

@boegel
Copy link
Member Author

boegel commented Jun 22, 2017

@Falkor What's the use case you have in mind?

@Falkor
Copy link

Falkor commented Jun 22, 2017

I just updated the easybuild recipes for Likwid that relies on the likwid-accessD daemon (built under $EBROOTLIKWID/sbin) to forwards the read and write requests to the MSR registers with higher priviledges as per [power] checks -- you will soon have the merge requests.

There are 3 ways to do that (setuid / setgid or libcap methods), only the first one actually works, but in all cases it would be worth to give the [sudo] commands to perform to the user.
So far, and unless I'm wrong, I can only do that by adding some messages as part of the postinstallcmds, typically as follows:

postinstallcmds = [
    'echo "IMPORTANT: you will have to manually apply the following changes:"',
    'echo "  sudo chown root:root \$EBROOTLIKWID/sbin/likwid-accessD && sudo chmod u+s \$EBROOTLIKWID/sbin/likwid-accessD"'
]

but that hides it in the build logs as they are not exposed to the user on the regular eb process.
In this case, having the possibility to provide post messages would be grateful.

@boegel boegel modified the milestones: 3.4.0, 3.x Jun 22, 2017
@boegel boegel modified the milestones: 3.5.0, 3.4.0 Sep 4, 2017
@boegel boegel modified the milestones: 3.5.0, next release Dec 6, 2017
@boegel boegel modified the milestones: 3.5.1, 3.6.0 Jan 12, 2018
@boegel boegel modified the milestones: 3.5.2, 3.6.0 Feb 22, 2018
@boegel boegel modified the milestones: 3.6.0, 3.x Mar 14, 2018
@boegel
Copy link
Member Author

boegel commented Mar 14, 2018

@victorusu was looking for suggestions for contributions, maybe this is an easy one to tackle...

@boegel boegel modified the milestones: 3.x, 4.x Feb 20, 2020
PetrKralCZ added a commit to PetrKralCZ/easybuild-framework that referenced this issue Dec 20, 2022
@PetrKralCZ
Copy link
Contributor

I have implemented a solution with following usage:

postinstallmsgs = ["This is post install message 1", "This is post install message 2"]
== installing...
== ... (took 2 secs)
== taking care of extensions...
== ... (took < 1 sec)
== restore after iterating...
== ... (took < 1 sec)
== postprocessing...
== This is post install message 1
== This is post install message 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants