And looking through the ruby code for provider launchd I see this:
# start the service. To get to a state of running/enabled, we need to
# conditionally enable at load, then disable by modifying the
plist file
# directly.
def start
job_path, job_plist = plist_from_label(resource[:name])
did_enable_job = false
cmds = []
cmds << :launchctl << :load
if self.enabled? == :false # launchctl won't load disabled
jobs
cmds << "-w"
did_enable_job = true
end
cmds << job_path
begin
execute(cmds)
rescue Puppet::ExecutionFailure
raise Puppet::Error.new("Unable to start service: %s at
path: %s" % [resource[:name], job_path])
end
# As load -w clears the Disabled flag, we need to add it in
after
if did_enable_job and resource[:enable] == :false
self.disable
end
end
So I guess the -w switch is actually used... not sure where to go from
here.
Anyone?
/John
On 30 Aug, 15:33, grandpa <john.axel.eriks...@gmail.com> wrote:
> Talking to myself here ;-)... I've noticed in the man pages for
> launchctl in Snow Leopard this:
>
> -w Overrides the Disabled key and sets it to false. In previous
> versions, this option would modify the configuration file. Now the
> state of the Disabled key is stored elsewhere on-disk.
>
> So I guess the behavior DID change... whatever "previous versions"
> mean.
>
> Should I file a bug report?
>
> /John
>
> On 30 Aug, 15:30, grandpa <john.axel.eriks...@gmail.com> wrote:
>
>
>
> > Forgot to add that I'm running Snow Leopard...
>
> > I've noticed that to start the ssh server from terminal I must do:
> > launchctl load -w /System/Library/LaunchDaemons/ssh.plist
>
> > Notice the -w switch. Without it I just get "nothing found to load"...
>
> > I wonder if this is new to Snow Leopard?
>
> > /John
>
> > On 30 Aug, 15:06, grandpa <john.axel.eriks...@gmail.com> wrote:
>
> > > Anyone out there who've tried updating sshd_config on macs and
> > > restarting / ensure running the ssh server?
>
> > > I've found that this ALMOST works:
>
> > > service {
> > > "com.openssh.sshd":
> > > enable => true,
> > > ensure => running;
> > > }
>
> > > and then notifying that when changing the config... At least,
> > > com.openssh.sshd is what launchd calls the
> > > service.
>
> > > The problem is this though:
>
> > > err: //macssh/Service[com.openssh.sshd]: Failed to call refresh on
> > > Service[com.openssh.sshd]: Unable to start service: com.openssh.sshd
> > > at path: /System/Library/LaunchDaemons/ssh.plist...
>
> > > Anyone good with OS X / Puppet who could enlighten me?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
