search for: setsid

Hi All, I compiled the 3.2.3p1 source on SCO OpenServer 5.0.6. When a client connects to it now, they get stair-stepping everywhere. Issuing an stty sane resolves the issue for that login. For bug 245 in 3.2.2p1, the call to setsid() is sshd.c was bypassed due to problems it was causing with Solaris. However, by allowing this method to be called, the stair-stepping goes away. Thanks, Greg Jewell

...SH_ASKPASS=<password_script> and DISPLAY=nodisplay. My password_script just contains echo "password", nothing else. Now if I execute this ssh command: ssh -T jan@<dest_host> "/<script_dir>/<script>" It still asks me for a password. This command though setsid ssh -T jan@<dest_host> "/<script_dir>/<script>" does work as expected, it launches the remote script. I know ssh should support this out of the box, so I want to get rid of setsid. Any help or directions are appreciated. Warm regards, Jan

Hi Folks, I want to set up backgroundrb on my laptop to do some tests. But when I run "scripts/background start" I get this error: ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in `setsid'': the setsid() function is unimplemented on this machine (NotImplementedError) from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in `call_as_daemon'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:191:in `start_proc'...

Hi, Just thinking about the possibility of a Process.setsid for Windows. Would a Process.setsid analogue for Windows be a matter of calling CreateProcess() with CREATE_NEW_PROCESS_GROUP + DETACHED_PROCESS ? And raise an error instead if the current process is the process group leader? Regards, Dan

http://bugzilla.mindrot.org/show_bug.cgi?id=245 ------- Additional Comments From dtucker at zip.com.au 2002-12-14 00:36 ------- Did some digging on this. Carson seems to be correct in that the problem is due to missing controlling terminal. I uncommented the setsid() in sshd.c and added some debugging log() calls to sshd, which generated the following: sshd[21690]: main: before setsid sid=21460 sshd[21690]: main: after setsid sid=21690 sshd[21690]: Accepted publickey for dtucker from 192.168.1.1 port 1665 ssh2 sshd[21694]: pty_make_controlling_tty called, t...

H. Peter Anvin dixit: >But is that really a tty, then? I also understand that virtio console Hm. Both eglibc and dietlibc return true for isatty on it. >doesn't support termios, which makes this an ugly bifurcation. All of Let me test that? quick? hah not really (CONFIG_VIRTIO_CONSOLE=m)? ok luckily Ubuntu?s linux-image-3.15.0-5-generic is installable on Debian stable and has

...getcwd getaddrinfo getgrouplist getnameinfo getrlimit getrusage getttyent getusershell glob inet_aton inet_ntoa inet_ntop innetgr login_getcapbool md5_crypt memmove mkdtemp on_exit openpty realpath rresvport_af setdtablesize setenv setegid seteuid setlogin setproctitle setresgid setreuid setrlimit setsid sigaction sigvec snprintf strerror strlcat strlcpy strmode strsep strtok_r sysconf tcgetpgrp utimes vsnprintf vhangup vis waitpid _getpty __b64_ntop +for ac_func in arc4random atexit b64_ntop bcopy bindresvport_sa clock fchown fchmod freeaddrinfo futimes gai_strerror getcwd getaddrinfo getgrouplist...

I need ssh-add to fail cleanly if it tries and fails to read a key, rather than prompting the user. I can't seem to figure out how to do that. This is on a Linux 2.6.26 system, running OpenSSH 5.1p1 (as built on debian lenny/sid) First, the things i've tried: * i've unset the DISPLAY and SSH_ASKPASS environment variables, so no X11-style prompting should happen. * i've

Hi, all, I pressed Ctrl+C in R process, and found that the child process which was spawned by using "pipe" is terminated due to this. Are there any way to work around it, so that the child process can run happily without being terminated? Or can we block the signal for the child process? 1. I used pipe to spawn one C++ process, which will running in a loop without exiting immediately.

Don't know why it works, but it works ... Rich.

Does ctrl+c work? My experience with (non klibc) init=/bin/bash is that getting ctrl+c to work requires some jumping through hoops, because running as pid 1 doesn't really work. If I recall correctly you have to call setsid, and open a tty as a controlling tty, you can't call setsid as pid 1. The hack that I got to work (for reference, I'm using this for raw kernel testing qemu-kvm) is: kernel command line: init=/boot/mz-boot.sh $ cat /boot/mz-boot.sh #!/bin/bash main() { echo 'Init (hostname, HOSTN...

...or the initial attempt to start B once the background script has been started to implement the DNS check and eventually the delayed start of B. Unfortunately, I cannot find a way to force libvirt to continue until the background script exits. No combination of background execution, nohup, disown, setsid -f, or at seems to detach the process sufficiently to "fool" libvirt into acting on the "exit 1" line in the qemu script and proceed on to start other guests. As a result, the dependency of B on A deadlocks, and neither guest ever starts. Can someone please either find an erro...

...r start" does not always suffice. But building a boot environment is a bit tedious, you'd almost want some command to take care of that for you -- alas none exists. However the boot environment is usually very simple, which can be approximated with something like: ( cd / && setsid env -i /sbin/service whichever start ) With SELinux it is critical to run it in a more useful context: ( cd / && /usr/sbin/run_init setsid env -i /sbin/service whichever start ) If run_init isn't installed the following gives a similar result: ( cd / && runcon -u system_...

I compiled OpenSSH 3.6.1p1 on NCR MP-RAS v4.3 (or at least "uname -a"'s output of 4.0.3.0 suggests v4.3, I'm not positive). I was able to compile zlib (1.1.4) and openssl (0.9.7a) with little trouble. OpenSSH took hand-hacking the includes.h file as follows: diff -cr openssh-3.6.1p1/includes.h openssh-3.6.1p1-customized/includes.h *** openssh-3.6.1p1/includes.h Sun Oct 20

http://bugzilla.mindrot.org/show_bug.cgi?id=245 ------- Additional Comments From wknox at mitre.org 2002-05-18 00:58 ------- Same issue with Solaris 8 built with gcc 2.95.2 with the following configure options: --without-rsh --with-tcp-wrappers --with-pam --disable-suid-ssh --with-prngd-socket --with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin Running a ssh -v

...*/ ! if (on_exit(cleanup_socket, NULL) < 0) { int saved = errno; cleanup_socket(); packet_disconnect("socket: %.100s", strerror(saved)); *** ssh-agent.c Fri May 11 16:05:57 2001 --- ssh-agent.c.new Fri May 11 16:07:20 2001 *************** *** 860,866 **** perror("setsid"); cleanup_exit(1); } ! if (atexit(cleanup_socket) < 0) { perror("atexit"); cleanup_exit(1); } --- 860,870 ---- perror("setsid"); cleanup_exit(1); } ! /* This is bad...on_exit requires 2 parameters, whereas ! at_exit only...

Changes: * Removed utimes() posix hack since scp.c moved to utimes() * Fixed waitpid() to be more proper. It was driving me nuts. * Made setsid() a #define in next-posix.h * Removed WCOREDUMP() from next-posix.h since we really don't support it and now #ifdef .. #else .. #endif around the single place it was used. * Fixed typecasting issue in sshd.c with sizeof() returning "long int" on next when we expect "int&quo...

...ust I tried to upgrade openssh from 3.5p1 to 3.6.1p2 on Reliant Unix 5.45 and run into this error: root at soltest: tail /var/adm/log/messages .... May 23 15:45:28 soltest unix: sshd[4013]: Accepted password for root from 10.128.11.72 port 2624 ssh2 May 23 15:45:28 soltest unix: sshd[4101]: error: setsid: Not owner May 23 15:45:28 soltest unix: sshd[4101]: error: open /dev/tty failed - could not set controlling tty: No such device or address The shell tells me that she has no controlling tty root at soltest: ps ps: can't find controlling terminal root at soltest: bash bash: no job control in...

On Fri, Nov 06, 2015 at 07:23:59PM -0800, Gordon Messmer wrote: > On 11/06/2015 06:30 PM, Jobst Schmalenbach wrote: > >What troubles me that a simple restart of the daemon fixes everything but it does not come up on reboot. > > Running the service script manually may not give you the same > selinux context as on boot. Services should be started using > "run_init"

...mment #5 from djm at mindrot.org 2006-03-13 16:00 ------- This isn't an SSH bug, your SIGHUPs are a result of the process' controlling terminal going away. You can either: 1. Run without a pty as Darren suggested 2. Ensure that startx is called without a controlling terminal. Linux has a setsid(8) command for this, otherwise you might be able to use something like: perl -e 'use POSIX ; setsid();' 3. Make your script stick around until the X session exits by not backgrounding itself or by explictly calling the "wait" shell builtin. ------- You are receiving t...