SlickEdit Product Discussion > SlickEdit®
26.0.3.1: Can no longer build when ssh into another machine
rowbearto:
I often like to ssh into a different machine manually from the "Build" tool window and then run the "Build" command in SlickEdit.
This worked fine in previous releases.
But now in 26.0.3.1 when I try to do this I get an error:
--- Code: --- /home/rbresali/pen/slickedit/se_26000301_linux64/bin/vsbuild -signal vsbuild_done -commandfile "/tmp/slk.486800.20220713162217087.-6.cmf"
/home/rbresali/pen/slickedit/se_26000301_linux64/bin/vsbuild -signal vsbuild_done -commandfile "/tmp/slk.486800.20220713162217087.-6.cmf"
ERROR: Could not open arg file '/tmp/slk.486800.20220713162217087.-6.cmf'
--- End code ---
As I have sshed somewhere else then vsbuild is running on a different machine then SlickEdit. That machine has a different /tmp directory, so SlickEdit is not able to find it.
I would really like to be able to get this ability back.
patrick:
Ah, it's referencing a local arguments file. I may need to put in a configuration option so you can disable it for this case. I'll look and see what I can do.
rowbearto:
Patrick:
This issue is still there in beta2. Any way I can get this functionality back?
patrick:
In beta 3, you'll be able to set "def_allow_vsbuild_use_commandfile" to 0 and get back the old behavior where it isn't referencing a commandfile on the local filesystem.
rowbearto:
Thanks Patrick.
What is this new feature with def_allow_vsbuild_use_commandfile set to non-zero?
Why not have the old behavior as the default and the new behavior be non-default?
Navigation
[0] Message Index
[#] Next page
Go to full version