Re: How to get portinstall to 'shut up' so I can run it in background
Doug Barton wrote: On Mon, 3 Dec 2007, Wes Morgan wrote: On Tue, 4 Dec 2007, Stefan Sperling wrote: Screen also has log functionality. Toggle with: Ctrl+A, then Shift+H You can also use script to capture the output fairly easily. So you have to use two different programs, one of which is a port, to accomplish what nohup will do by itself. :) My point being that a lot of people seem to think that screen(1) is the answer, no matter what the question, when often simpler answers exist. If you're one of those people, that's fine, I learned a long time ago I'm not going to change your mind. But I do think it's useful to note that there are other valid solutions, even if simply for completeness sake. Maybe I am doing something wrong, but I have never been able to get nohup to work correctly with portupgrade for this sort of this. For example: ianto# nohup portupgrade -a /tmp/port.log [1] 6238 ianto# [1] + Suspended (tty output)portupgrade -a /tmp/port.log ianto# ianto# cat /tmp/port.log ianto# I've never had time to figure out why it suspends, though. Anyone know? Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get portinstall to 'shut up' so I can run it in background
Ben Kelly wrote: Maybe I am doing something wrong, but I have never been able to get nohup to work correctly with portupgrade for this sort of this. For example: ianto# nohup portupgrade -a /tmp/port.log You just want to do 'nohup portupgrade -a ' output will be captured in nohup.out. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get portinstall to 'shut up' so I can run it in background
Doug Barton wrote: Ben Kelly wrote: Maybe I am doing something wrong, but I have never been able to get nohup to work correctly with portupgrade for this sort of this. For example: ianto# nohup portupgrade -a /tmp/port.log You just want to do 'nohup portupgrade -a ' output will be captured in nohup.out. Ben is right. When you run portupgrade with nohup and background the process -- either with '' or by ctrl-z followed with a bg -- it gets suspended until the job is brought back to the foreground. Portupgrade acts very strangely when it's not attached to a tty. -- Russell A. Jackson [EMAIL PROTECTED] Network Analyst California State University, Bakersfield He asked me if I knew what time it was -- I said yes, but not right now. -- S. Wright ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get portinstall to 'shut up' so I can run it in background
On Mon, Dec 03, 2007 at 02:53:12PM -0800, Doug Barton wrote: Clint Olsen wrote: I've tried redirecting standard output/error, both /bin/sh and /bin/csh, and I can't run this in batch. I'm trying to build gnome which takes hours, and I want it backgrounded so that if this SSH shell disconnects it doesn't crater the build. You would think that --batch would make this happen, but no go. While I know screen(1) has a lot of devotees, you could almost certainly use nohup for this same purpose, with the pleasant side effect that you will have a log of what happened on disk in case something blows up. Screen also has log functionality. Toggle with: Ctrl+A, then Shift+H -- stefan http://stsp.name PGP Key: 0xF59D25F0 pgpSrrbXvDRxg.pgp Description: PGP signature
Re: How to get portinstall to 'shut up' so I can run it in background
On Nov 27, Wes Morgan wrote: Why not just run the build inside a screen session? Getting disconnected would have no effect on it then. Thanks to Wes and Matthew for a terrific suggestion. Screen just ain't for 80's work :) -Clint -- Clint Olsen. -- . clint at NULlsen dot net .' ,-. `. ;_,' ( ; I am Dick Lexic of Borg. Prepare to be ass-laminated. `.``;' -- Styx Allum ` -- ' ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get portinstall to 'shut up' so I can run it in background
On Nov 28, 2007 1:36 AM, Clint Olsen [EMAIL PROTECTED] wrote: I've tried redirecting standard output/error, both /bin/sh and /bin/csh, and I can't run this in batch. I'm trying to build gnome which takes hours, and I want it backgrounded so that if this SSH shell disconnects it doesn't crater the build. You would think that --batch would make this happen, but no go. Thanks, -Clint Hi Clint, Hope this help portinstall --batch pkgname /dev/null 21 but I would recommend using screen. regards Paul B ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
How to get portinstall to 'shut up' so I can run it in background
I've tried redirecting standard output/error, both /bin/sh and /bin/csh, and I can't run this in batch. I'm trying to build gnome which takes hours, and I want it backgrounded so that if this SSH shell disconnects it doesn't crater the build. You would think that --batch would make this happen, but no go. Thanks, -Clint ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get portinstall to 'shut up' so I can run it in background
On Nov 27, 2007, at 5:41 PM, Wes Morgan wrote: On Tue, 27 Nov 2007, Clint Olsen wrote: I've tried redirecting standard output/error, both /bin/sh and / bin/csh, and I can't run this in batch. I'm trying to build gnome which takes hours, and I want it backgrounded so that if this SSH shell disconnects it doesn't crater the build. You would think that --batch would make this happen, but no go. Why not just run the build inside a screen session? Getting disconnected would have no effect on it then. That's the only option that I know of other than building an item locally or batching via cron... besides, ssh times out connections after a while anyhow, so it's toast anyways if you don't do screen or a local build... -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
