You are right, this works now. Thank you very much for your help! On Thu, Mar 22, 2012 at 6:42 PM, Rayson Ho <[email protected]> wrote:
> On Thu, Mar 22, 2012 at 1:32 PM, P. Golik <[email protected]> wrote: > > I already tried that, but I experienced a strange effect: > > So, qlogin is just a symlink to qsh, right? > > Actually, I just read the code again - and yes, qrsh & qlogin are the > same binary, so I was searching for references for the > opt_list_append_opts_from_default_files() function in the wrong > directory when I replied to your email earlier. > > So yes, it looks like a bug, and still as a quick workaround the > wrapper method should be a quick & dirty fix... > > Can you try the wrapper method again by placing the real qlogin in a > seperate directory, like: > > #!/bin/sh > > # call the real qlogin: > <path/real>/qlogin -pty n $* > exit $? > > As the code only checks for the basename, it should work this time. > (Again, I have not tried it before... but this should work with the > code.) > > Rayson > > > > > > > > If I run it as it is right now, it looks like this: > > > > $ qlogin > > Your job 6353576 ("QLOGIN") has been submitted > > waiting for interactive job to be scheduled ... > > Your interactive job 6353576 has been successfully scheduled. > > Establishing /sge-8.0.0/bin/qlogin_ssh_wrapper.sh session to host myhost > ... > > > > Which is fine, I get my session started on myhost. > > > > But when I move qlogin to qlogin.real to use the wrapper like you > suggested, > > a call to the symlink looks like this: > > > > $ ls -l $(which qlogin.real) > > lrwxrwxrwx 1 root root 3 2012-03-22 18:19 > > /sge-8.0.0/bin/lx-amd64-c11/qlogin.real -> qsh > > > > $ qlogin.real > > Your job 6353578 ("INTERACTIVE") has been submitted > > waiting for interactive job to be scheduled ... > > Could not start interactive job. > > > > And no session gets started. Does qsh detect somehow how it was started? > > > > > > On Thu, Mar 22, 2012 at 6:15 PM, Rayson Ho <[email protected]> > wrote: > >> > >> I think a quick way is to wrap around it using a shell script: > >> > >> #!/bin/sh > >> > >> # call the real qlogin: > >> qlogin.real -pty n $* > >> exit $? > >> > >> Give it a try... > >> > >> Rayson > >> > >> > >> > >> On Thu, Mar 22, 2012 at 1:13 PM, P. Golik <[email protected]> wrote: > >> > Uh, I see. Is there another way to make "-pty n" default for qlogin? > >> > > >> > > >> > On Thu, Mar 22, 2012 at 6:12 PM, Rayson Ho <[email protected]> > >> > wrote: > >> >> > >> >> On Thu, Mar 22, 2012 at 12:59 PM, P. Golik <[email protected]> > wrote: > >> >> > So, to me it looks like qlogin doesn't respect -pty n if set via > >> >> > sge_request. Is it a bug, or do I have to consider anything special > >> >> > about > >> >> > this setup? > >> >> > >> >> It is not a bug, it is just that qlogin does not read the > >> >> common/sge_request file at all. > >> >> > >> >> Rayson > >> >> > >> >> > >> >> > >> >> > > >> >> > Thanks! > >> >> > > >> >> > P. > >> >> > > >> >> > _______________________________________________ > >> >> > users mailing list > >> >> > [email protected] > >> >> > https://gridengine.org/mailman/listinfo/users > >> >> > > >> > > >> > > > > > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
