Project

General

Profile

Bug #7464

svcadm does not exist - so syslog is never restarted on Solaris

Added by Jonathan CLARKE about 4 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

(introduced in #5846)

Associated revisions

Revision 1c2f8629 (diff)
Added by Jonathan CLARKE about 4 years ago

Fixes #7464: svcadm does not exist - so syslog is never restarted on Solaris

Revision a996cda7
Added by Benoît PECCATTE about 4 years ago

Merge pull request #783 from jooooooon/bug_7464/paths_path_svcadm_does_not_exist_so_syslog_is_never_restarted_on_solaris

Fixes #7464: svcadm does not exist - so syslog is never restarted on Solaris

History

#1

Updated by Jonathan CLARKE about 4 years ago

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE
#2

Updated by Jonathan CLARKE about 4 years ago

  • Subject changed from ${paths.path[svcadm]} does not exist - so syslog is never restarted on Solaris to svcadm does not exist - so syslog is never restarted on Solaris
  • Status changed from In progress to New
  • Assignee deleted (Jonathan CLARKE)
#3

Updated by Jonathan CLARKE about 4 years ago

  • Status changed from New to Pending technical review
  • Assignee set to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/783
#4

Updated by Jonathan CLARKE about 4 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#6

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.12 and 3.1.5 which were released today.

Also available in: Atom PDF