Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: nohup dies
- X-seq: zsh-users 11904
- From: "Pau Amaro-Seoane" <vim.unix@xxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: nohup dies
- Date: Sun, 30 Sep 2007 21:56:46 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=U3s6cygIvciev/lNePnPCXS73+FUaFuzop9eSyjRc38=; b=lTP+kBNAbHG0h+gbhPCzaSowAi7fFRhp7PzkieO1dCU+dyL3sLKCQO9qbjbcDKivGP/HlAk+MrW3Y6oJ9lKVnsOkGGXOmZ7UY9H5Ow7hxpcHxaZbVDrKns+loPQLyzNHimmB1ISNiE18R/bZIP5YDS5cJHcQA+lPOj9ZBZU7Nq8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=I5l5M2jfAElZE8f2g3DF+8e+g49hznjVXrWEBshPjxOMKUu3v0Ol1YHar9WMy0D4W98Wy9aYwk4WjCuXcTxHJoZkPXv5HCbMW0zj10quFXRKoX8SadCuN7Hb9u0jcbYZxByqAX923MVp5c4ahbtlGAKsamHmFomMEgg5nEltdl0=
- In-reply-to: <200709291256.l8TCuak4003565@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <vim.unix@xxxxxxxxxxxxxx> <30c383e70709290023x46dc7d13o2ff3904a05413496@xxxxxxxxxxxxxx> <200709291256.l8TCuak4003565@xxxxxxxxxxxxxxxxxxx>
- Reply-to: vim.unix@xxxxxxxxx
| Just "setopt nohup" in your initialisation file
nope...
I tried that and the process died again... Same error
The only way is to start the simulation from ksh. Zsh stubbornly
refuses to nohup it...
I didn't try emulate ksh since I stick to zsh syntax and have billions
of zsh scripts.
Pau
2007/9/29, Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>:
> "Pau Amaro-Seoane" wrote:
> > > nohup is not a shell builtin; it's simply an executable programme that's
> >
> > man nohup
> >
> > (...)
> > NOTE: your shell may have its own version of nohup, which
> > usually supersedes the version described
> > here. Please refer to your shell's documentation for details
> > about the options it supports.
> > (...)
>
> Yes, I'm well aware nohup *may* be a shell builtin, but in zsh it
> isn't. The easy way to check is to run "which nohup".
>
> > > A lot of other shells, I presume (but I haven't actually checked)
> > > including ksh, don't send SIGHUP to processes when the shell exits.
> >
> > But zsh is supposed to emulate ksh, right?
>
> Not unless you have "emulate ksh" in effect. If you do, "setupt nohup"
> is turned on and you have the same (global) effect as in ksh (you don't
> need the "nohup" command at all).
>
> > nohup whatever should work regardless of shell.
>
> "nohup" does work; as I pointed out you're using it the wrong way. The
> difference in ksh is that you don't need it at all; it's harmless if you
> do use it, but ksh doesn't send the HUP signal anyway.
>
> > And it _did_ in the
> > older version of zsh, now not anymore. Can you tell me why?
>
> Nothing here has changed, but as I suggested before your old setup may
> have had the "nohup" option turned on.
>
> > the "solution" for now is to launch the simulation with ksh... or
> > resort to screen... but it's a pity, I stick to zsh a lot
>
> Just "setopt nohup" in your initialisation file, or "emulate ksh" if
> you're set on ksh syntax generally.
>
> --
> Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
> Web page now at http://homepage.ntlworld.com/p.w.stephenson/
>
Messages sorted by:
Reverse Date,
Date,
Thread,
Author