Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edited following @chriscool feedback #2180

Merged
merged 1 commit into from
Jan 23, 2016
Merged

Edited following @chriscool feedback #2180

merged 1 commit into from
Jan 23, 2016

Conversation

RichardLitt
Copy link
Member

See dec4a72

License: MIT
Signed-off-by: Richard Littauer richard.littauer@gmail.com

@RichardLitt
Copy link
Member Author

cc @chriscool

@chriscool
Copy link
Contributor

Yeah, LGTM.

@whyrusleeping
Copy link
Member

@RichardLitt looks like some tests are failing, could you go ahead and fix those before we merge this?

@whyrusleeping
Copy link
Member

I don't know if I like this phrasing, its unclear to me what it means

@Ape
Copy link

Ape commented Jan 11, 2016

I think the previous version is better. We want to say that you can use SIGTERM or SIGINT to shutdown the daemon, for example with Ctrl-C. And that another signal will kill it forcibly.

EDIT: What about this:

To shutdown the daemon, send SIGTERM or SIGINT signal to it. This can be done using Ctrl-C or kill. It may take a while for the daemon to shutdown gracefully, but it can be killed forcibly by sending the signal again.

EDIT2: Also, I don't know how the daemon actually reacts currently, but I think this is the desired behavior:

  • SIGTERM shutdowns the daemon gracefully. Repeating the signal does nothing.
  • SIGINT shutdowns the daemon gracefully, except if the daemon is already shutting down then shutdown forcibly.
  • SIGKILL forcibly kills the daemon. (The daemon couldn't prevent this.)

@chriscool
Copy link
Contributor

This is nice as it teaches the user things, but then why not:

To shutdown the daemon, send SIGTERM or SIGINT signal to it. This can be done using respectively kill or Ctrl-C. It may take a while for the daemon to shutdown gracefully, but it can be killed forcibly by sending the signal again.

Also it doesn't address people on Windows who may not use the command line at all.

@Ape
Copy link

Ape commented Jan 11, 2016

We don't have to say that Ctrl-C sends a SIGINT. On the other hand, we should specify SIGTERM since it can be sent with any external program.

To shutdown the daemon, press Ctrl-C or send SIGTERM signal to it (e.g. with kill). It may take a while for the daemon to shutdown gracefully, but it can be killed forcibly by pressing Ctrl-C again.

@RichardLitt
Copy link
Member Author

I've edited it, again. Thoughts?

@Ape
Copy link

Ape commented Jan 12, 2016

I would prefer the version on my previous comment, because we don't really need to say that Ctrl-C emits a SIGINT, but instead try to keep it simple and short. This isn't very important issue, though.

Also, I think you duplicated the paragraph there.

License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>
@RichardLitt
Copy link
Member Author

Changed. Ctrl+C only works on unix, but it is useful for some users. I think this one is fine.

@rht
Copy link
Contributor

rht commented Jan 15, 2016

It'd be useful / more discoverable to add a brief line such as "hit C-c again to force-shutdown the daemon" at https://github.com/ipfs/go-ipfs/blob/master/cmd/ipfs/daemon.go#L153.

@rht
Copy link
Contributor

rht commented Jan 23, 2016

Other than the small UX comment, this LGTM.

rht added a commit that referenced this pull request Jan 23, 2016
@rht rht merged commit f5b8c7c into master Jan 23, 2016
@rht rht deleted the feature/shutdown branch January 23, 2016 05:24
@jbenet
Copy link
Member

jbenet commented Jan 23, 2016

LGTM.

It'd be useful / more discoverable to add a brief line such as "hit C-c again to force-shutdown the daemon" at https://github.com/ipfs/go-ipfs/blob/master/cmd/ipfs/daemon.go#L153.

Yes, specifically at https://github.com/ipfs/go-ipfs/blob/master/cmd/ipfs/daemon.go#L163

RichardLitt added a commit that referenced this pull request Jan 24, 2016
See #2180 (comment)

License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>
RichardLitt added a commit that referenced this pull request Jan 24, 2016
See #2180 (comment)

License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>
SgtPooki added a commit that referenced this pull request Dec 2, 2023
## [4.2.0](ipfs/ipfs-webui@v4.1.1...v4.2.0) (2023-12-02)


 CID `bafybeidf7cpkwsjkq6xs3r6fbbxghbugilx3jtezbza7gua3k5wjixpmba`

 --- 



### Features

* peers table can be filtered ([#2181](ipfs/ipfs-webui#2181)) ([37b5880](ipfs/ipfs-webui@37b5880))
* **pinning:** add Scaleway pinning service ([#2132](ipfs/ipfs-webui#2132)) ([0cc3b04](ipfs/ipfs-webui@0cc3b04))


### Bug Fixes

* error loading scaleway template URL ([7a3388e](ipfs/ipfs-webui@7a3388e))
* replace estuary with web3 for pinning ([#2182](ipfs/ipfs-webui#2182)) ([e2fc7c8](ipfs/ipfs-webui@e2fc7c8))
* status page supports webrtc ([#2180](ipfs/ipfs-webui#2180)) ([ff75d4e](ipfs/ipfs-webui@ff75d4e)), closes [#1965](ipfs/ipfs-webui#1965)
* switch to new dnslink updater ([#2175](ipfs/ipfs-webui#2175)) ([a63f48a](ipfs/ipfs-webui@a63f48a))


### Trivial Changes

* Pull transifex translations ([#2162](ipfs/ipfs-webui#2162)) ([c0f8f54](ipfs/ipfs-webui@c0f8f54))
* pull transifex translations ([#2177](ipfs/ipfs-webui#2177)) ([7f377ff](ipfs/ipfs-webui@7f377ff))
* update release transifex links ([74cce69](ipfs/ipfs-webui@74cce69))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants