On Wednesday, 3 October 2012 22:45:11 UTC-4, Jo wrote:
On Oct 1, 2012, at 5:00 PM, Lunixer wrote:
I'll try strace instead of tcpdump, being that this is not a TCP
communication problem over the wire but rather a file or directory access
problem.
Um, no. Puppet client talks to the server over the network, even on the
same host. You really should listen to advice we provide.
On Oct 1, 2012, at 5:00 PM, Lunixer wrote:
I'll try strace instead of tcpdump, being that this is not a TCP
communication problem over the wire but rather a file or directory access
problem.
Um, no. Puppet client talks to the server over the network, even on the
same host. You really should listen to advice we provide.
do you think a tcpdump will show? The exact same error message.
This is why you would use strace, to see what is happening inside the
actual process.
Try not being so condescending, particularly when you're wrong.
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DP9BCccRLqEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
