Never mind .. I see it get set when building shared .. I am just trying to see how the Macros get expanded.

Hi,

How do I turn on IOIL_PRELOAD for the build?

Thanks.

Colin

Greetings,

Just a couple quick questions:

1. What is the difference between “aliased intercept” and “single intercept”?
2. What’s the purpose of __wrap_XXX definition?

Example:
__attribute__((visibility("default"))) int __wrap_fclose (FILE *) __attribute__((weak, alias("dfuse_" "fclose")));

Thanks.

Colin

Hi,

How do I turn on IOIL_PRELOAD for the build?

Thanks.

Colin

Greetings,

Just a couple quick questions:

1. What is the difference between “aliased intercept” and “single intercept”?
2. What’s the purpose of __wrap_XXX definition?

Example:
__attribute__((visibility("default"))) int __wrap_fclose (FILE *) __attribute__((weak, alias("dfuse_" "fclose")));

Thanks.

Colin

Greetings,

Just a couple quick questions:

1. What is the difference between “aliased intercept” and “single intercept”?
2. What’s the purpose of __wrap_XXX definition?

Example:
__attribute__((visibility("default"))) int __wrap_fclose (FILE *) __attribute__((weak, alias("dfuse_" "fclose")));

Thanks.

Colin

Hi,

Just sent my webchat account to your email.

Thanks.

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of timehuang88@...
Sent: Wednesday, June 3, 2020 9:33 AM
To: daos@daos.groups.io
Subject: Re: [daos] missing protoc-gen-c

Hi Zhang, Jiafu

Hi Kevan.

We haven’t built anything into daos_agent to daemonize itself – the expectation is that in production that sort of thing will be handled by systemd. Maybe you could use a wrapper to cd / and then exec daos_agent ?

mjmac

Greetings,

Checking to see if this is a known issue.    We build DAOS in a NFS filesystem, as then we can log into any node in the cluster and use gdb with the source tree to debug a binary.   The binaries get installed in ~daos/daos/install, which is a local filesystem on each node.

What happens is that when we start the daos_agent on the node where we compiled DAOS, it ends up cd’d in directory daos/build/dev/gcc/src/cart/src/gurt in the NFS filesystem, so if we want to delete the daos source tree and start over, we can’t do so because there is a .nfs0000XXX file in that directory which prevents a “rm -rf daos” from succeeding.   We have to kill off the daos_agent in order to be able to delete the daos directory, then start the daos_agent again.

I suspect this is not intentional.  😊.  Known problem, or should I open a ticket?

Thanks, Kevan

Greetings,

Checking to see if this is a known issue.    We build DAOS in a NFS filesystem, as then we can log into any node in the cluster and use gdb with the source tree to debug a binary.   The binaries get installed in ~daos/daos/install, which is a local filesystem on each node.

What happens is that when we start the daos_agent on the node where we compiled DAOS, it ends up cd’d in directory daos/build/dev/gcc/src/cart/src/gurt in the NFS filesystem, so if we want to delete the daos source tree and start over, we can’t do so because there is a .nfs0000XXX file in that directory which prevents a “rm -rf daos” from succeeding.   We have to kill off the daos_agent in order to be able to delete the daos directory, then start the daos_agent again.

I suspect this is not intentional.  😊.  Known problem, or should I open a ticket?

Thanks, Kevan

Yes. It’s correct.

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of timehuang88@...
Sent: Tuesday, May 26, 2020 3:53 PM
To: daos@daos.groups.io
Subject: Re: [daos] problem: support Spark when compile java files

Hi Jiafu,
thx for your reply. 
since I build and install daos with the cmd below:

 scons --config=force --build-deps=yes install  PREFIX=/usr

so am i right to build java files like this cmd below:

$ mvn clean package -DskipITs -Ddaos.install.path=/usr

Yes that is the problem.  I have the bug commit but not the fix commit.   Can’t move forward at the moment, chasing another issue.

Thanks for the help,

Kevan

Hi Kevan.

What is the commit you’re working with? There was an agent config bug introduced in 2836ae4 and fixed in 12dfe6b.

Best,

mjmac

Greetings,

In file utils/config/daos_agent.yml the comments say that the default value for runtime_dir is /var/run/daos_agent and the default value for log_file is /tmp/daos_agent.log.   I don’t think this is true.   Given the text, I left the lines commented out in my latest config assuming I would get the defaults, but found that the daos_agent created its agent.sock file in ~daos, and it did not create a log file.   When I un-comment the two lines, the agent works as expected.

Seems like either the comments in that file should be changed, or daos_agent should honor those defaults.

Thanks, Kevan

Hi Kevan.

What is the commit you’re working with? There was an agent config bug introduced in 2836ae4 and fixed in 12dfe6b.

Best,

mjmac

Greetings,

In file utils/config/daos_agent.yml the comments say that the default value for runtime_dir is /var/run/daos_agent and the default value for log_file is /tmp/daos_agent.log.   I don’t think this is true.   Given the text, I left the lines commented out in my latest config assuming I would get the defaults, but found that the daos_agent created its agent.sock file in ~daos, and it did not create a log file.   When I un-comment the two lines, the agent works as expected.

Seems like either the comments in that file should be changed, or daos_agent should honor those defaults.

Thanks, Kevan

Greetings,

In file utils/config/daos_agent.yml the comments say that the default value for runtime_dir is /var/run/daos_agent and the default value for log_file is /tmp/daos_agent.log.   I don’t think this is true.   Given the text, I left the lines commented out in my latest config assuming I would get the defaults, but found that the daos_agent created its agent.sock file in ~daos, and it did not create a log file.   When I un-comment the two lines, the agent works as expected.

Seems like either the comments in that file should be changed, or daos_agent should honor those defaults.

Thanks, Kevan

Hi,

Do you have more error message? I cannot infer what cause is from your debug message. Just to make sure replace <daos_install> with your real path. If daos is installed to /usr/local/daos, your mvn command should be,

mvn clean package -DskipITs -Ddaos.install.path=/usr/local/daos

Thanks.

From: daos@daos.groups.io <daos@daos.groups.io> On Behalf Of timehuang88@...
Sent: Monday, May 25, 2020 8:23 PM
To: daos@daos.groups.io
Subject: [daos] problem: support Spark when compile java files

Hi there,

Just a heads up that master has moved from 18.04 to 20.04 for ubuntu support.

Cheers,

Johann