On 10/20/2014 09:16 PM, Claudio Freire wrote:
On Mon, Oct 20, 2014 at 3:30 PM, Erwin Waterlander
wrote: On 10/17/2014 04:18 PM, Claudio Freire wrote:
Cronjobs, using wcd inside a cron is probably not a very good idea, but someone might think it dandy to not have to type the whole path, and then you can run into trouble (not only the race condition of course, but it would be possible for wcd to race another wcd for sure). wcd is intended for interactive usage, not for scripts. I only have one nightly cron job that scans my home drive. For this the function is not needed, the binary can be called directly. I know, but people will abuse it. Be ready for bug reports. And it *is* a bug.
I am ready for bug reports. So far there is no report that anybody actually hit this problem. I admit it is possible that the problem can occur if two people on a shared account enter the wcd command in the same millisecond.
What's this reluctance to use the shell's PID as someone suggested? It's a trivial enough change.
I'm not reluctant to solve this issue. I may do that in a future version. I gave two possible workarounds on this list. Use the $WCDHOME variable, or use the -G option. I see it as a minor issue, not important enough to block the current version of wcd from Suse. best regards, Erwin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org