Re: Hello 1 question about close console
On 29/06/07, Steve W <[EMAIL PROTECTED]> wrote: On 25/06/07, Bill Moran <[EMAIL PROTECTED]> wrote: > In response to oim <[EMAIL PROTECTED]>: > > > Hello! > > > > I have a question about this situation. > > > > In home work Pc with FreeBSD Server, real ip and real domain name. > > When i remote connect ssh2 (consose) from my work.. make on server some.. compile program from ports > > > > And some time later i need to close console, but i want, what session not close and compile processing. > > > > If i disconect from console all job stop. How disconect from console and come back to my session? > > > > Thank you very much!!! > > Install/use /usr/ports/sysutils/screen > > -- > Bill Moran > http://www.potentialtech.com > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Oim, Bill's right, screen is a lifesaver. However, the man page is *enormous*, here's a synopsis: To make a new screen session (ie a console you can attach/detach to/from): $ screen -S "caterpillar" You will now find yourself in a new terminal. To list open screen sessions: $ screen -ls There is a screen on: 692976.caterpillar (Attached) 1 Socket in /tmp/uscreens/S-. Now, to leave this session open, and return to your previous shell: type CTRL + a, then d Now list again: $ screen -ls There is a screen on: 692976.caterpillar (Detached) 1 Socket in /tmp/uscreens/S-. If there's only one screen session, you can always re-attach to it directly with $ screen -d -r However, if there is more than one: $ screen -ls There are screens on: 692976.caterpillar (Detached) 460276.butterfly(Attached) 2 Sockets in /tmp/uscreens/S- ...you need to specify the one you want: $ screen -r 692976.caterpillar 90% of all I do with screen is with these commands. Hope this helps, Steve I forgot: to close a screen session: $ exit [screen is terminating] ...and you're back to your original shell (CTRL+D should work, too). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hello 1 question about close console
On 25/06/07, Bill Moran <[EMAIL PROTECTED]> wrote: In response to oim <[EMAIL PROTECTED]>: > Hello! > > I have a question about this situation. > > In home work Pc with FreeBSD Server, real ip and real domain name. > When i remote connect ssh2 (consose) from my work.. make on server some.. compile program from ports > > And some time later i need to close console, but i want, what session not close and compile processing. > > If i disconect from console all job stop. How disconect from console and come back to my session? > > Thank you very much!!! Install/use /usr/ports/sysutils/screen -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Oim, Bill's right, screen is a lifesaver. However, the man page is *enormous*, here's a synopsis: To make a new screen session (ie a console you can attach/detach to/from): $ screen -S "caterpillar" You will now find yourself in a new terminal. To list open screen sessions: $ screen -ls There is a screen on: 692976.caterpillar (Attached) 1 Socket in /tmp/uscreens/S-. Now, to leave this session open, and return to your previous shell: type CTRL + a, then d Now list again: $ screen -ls There is a screen on: 692976.caterpillar (Detached) 1 Socket in /tmp/uscreens/S-. If there's only one screen session, you can always re-attach to it directly with $ screen -d -r However, if there is more than one: $ screen -ls There are screens on: 692976.caterpillar (Detached) 460276.butterfly(Attached) 2 Sockets in /tmp/uscreens/S- ...you need to specify the one you want: $ screen -r 692976.caterpillar 90% of all I do with screen is with these commands. Hope this helps, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tftpd problems
Oliver Peter wrote: On Wed, Jun 20, 2007 at 04:04:56PM -0700, Mike Sweetser - Adhost wrote: I'm having problems setting up tftpd on FreeBSD 6.2-RELEASE - our Cisco routers cannot connect to the server, and only small files can be uploaded. Here's the line from inetd.conf: tftpdgram udp waitroot/usr/libexec/tftpd tftpd -w -l -s /home/tftproot When TFTPing from a Cisco router, a zero-byte file is created, and then a timeout occurs and it errors out. When TFTPing from a Windows XP machine, only about 20-30 bytes of the file are uploaded. No error is received, it says it completes the upload. Any ideas? My first try would be to have a look into /var/log/xferlog . Mike, Once I had problems with FBSD6.0's standard tftp server (/usr/libexec/tftpd) ignoring the blksize option as specified by clients. The symptoms were similar: transfers 'completed', but no/partial/unusable file. #tftp dgram udp waitroot/usr/libexec/tftpd tftpd -l -s /tftpboot #standard tftp server ignores client's blksize request (of 1432) and sends 512 byte blocks regardless #installed tftp-hpa-0.41 instead from port tftp dgram udp wait root /usr/local/libexec/in.tftpd in.tftpd -a 10.1.2.1:69 -T 50 -t 15 -v -s /usr/jail/usr/minibsd/boot HTH Best wishes, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
