Hi Ansis, I think it's a good idea. But printing only parent process might not be sufficient, we might have to print the entire process tree. An example of user ssh login and calls ovs-vsctl can be logged as below:
record 189: 2015-12-23 23:35:31.998 "ovs-vsctl: ovs-vsctl --no-wait add-br br88 -- comment (systemd(1)---sshd(741)---sshd(51100)---bash(51163)---my-ovs-vsctl.sh(78035))(FILE:./my-ovs-vsctl.sh,LINE:9)" With the format (process tree) followed by (filename, line number) Do you think this information is useful enough? Thanks Regards, William I just thought a little more about this. Third party code (e.g. libvirt) > also invokes ovs-vsctl and I believe it would be nice to be able to tell > such cases apart from those when user manually invoked ovs-vsctl manually > from ssh session or console. So parent process name would be helpful here. > > The FILE+LINE part could be used to troubleshoot potential OVS internal > bugs, for example, to quickly be able to tell which OVS internal code > changed OVSDB by calling ovs-vsctl. > > So how about printing both - PARENT PROCESS NAME+ID and FILE+LINE? > > > _______________________________________________ >> dev mailing list >> dev@openvswitch.org >> http://openvswitch.org/mailman/listinfo/dev >> > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
