Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 728
    • Issues 728
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 316
    • Merge requests 316
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • aportsaports
  • Issues
  • #174
Closed
Open
Issue created Sep 30, 2009 by Ted Trask@ttrask01Developer

Squid init.d stop fails when squid is crashed

Running ‘/etc/init.d/squid stop’ fails when squid is crashed. It should not fail but do the equivalent of ‘/etc/init.d/squid zap’.

squid 2.7.6-r11

To reproduce:
/etc/init.d/squid start
killall squid
/etc/init.d/squid stop

The status is then crashed instead of stopped. This is fairly serious because it prevents me from doing ‘/etc/init.d/networking restart’ because squid is in a weird state.

(from redmine: issue id 174, created on 2009-09-30, closed on 2009-10-09)

  • Changesets:
    • Revision c5bd8836 on 2009-10-02T15:08:51Z:
main/squid: remove pidfile if squis is not running

fixes #174
  • Revision a3a664b5 on 2009-10-02T15:09:58Z:
main/squid: remove pidfile if squis is not running

fixes #174
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking