네트워크에 연결되지 않은 경우 로컬 호스트 이름이 몇 초마다 변경됩니다.

어느 때까지도 노트북을 깨우지 만 네트워크에 연결되기 전에 다음과 유사한 메시지가 나타납니다.

This computer's local hostname
"sojourner-896.local" is already in use on
this network. The name has been changed
to "sojourner-972.local"

네트워크에 연결하지 않고 "확인"버튼을 클릭하지 않으면 호스트 이름이 계속 증가합니다. 네트워크 (유선 또는 무선)에 연결하면 이름의 수가 증가하지 않습니다.

호스트 이름이 5,000 - 6,000 범위 (2-3 일마다)에 들어 오면 "공유"환경 설정 패널에서 호스트 이름을 재설정합니다.

어떤 생각이 이것을 일으키는 것이겠습니까?

콘솔 앱을 통해 로그를 조사한 결과 네트워크에서 연결이 끊어 질 때마다 다음 로그가 생성되는 것을 발견했습니다.

8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7647.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7647.local. Addr 127.0.0.1
8/29/14 10:07:59.087 PM mDNSResponder[414]: Local Hostname sojourner-7647.local already in use; will try sojourner-7743.local instead
8/29/14 10:08:00.923 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7647.local" to "sojourner-7743.local"
8/29/14 10:08:00.944 PM configd[26]: setting hostname to "sojourner-7743.local"
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.146 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7743.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.456 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.457 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.457 PM mDNSResponder[414]: Local Hostname sojourner-7743.local already in use; will try sojourner-7765.local instead
8/29/14 10:08:04.365 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7743.local" to "sojourner-7765.local"
8/29/14 10:08:04.375 PM configd[26]: setting hostname to "sojourner-7765.local"
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:05.839 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7765.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:06.141 PM mDNSResponder[414]: Local Hostname sojourner-7765.local already in use; will try sojourner-7802.local instead
8/29/14 10:08:08.006 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7765.local" to "sojourner-7802.local"
8/29/14 10:08:08.016 PM configd[26]: setting hostname to "sojourner-7802.local"
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7802.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.733 PM mDNSResponder[414]: Local Hostname sojourner-7802.local already in use; will try sojourner-7837.local instead
8/29/14 10:08:11.578 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7802.local" to "sojourner-7837.local"
8/29/14 10:08:11.588 PM configd[26]: setting hostname to "sojourner-7837.local"
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7837.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7837.local.
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7837.local. Addr 127.0.0.1
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (17) for sojourner-7837.local. (Addr); rate limiting in effect
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (18) for sojourner-7837.local. (AAAA); rate limiting in effect
8/29/14 10:08:14.193 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.194 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.212 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:19.916 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7647 server: SOJOURNER-7837 indomain was: <NULL>
8/29/14 10:08:19.937 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7837 server: SOJOURNER-7837 indomain was: <NULL>

두 번째 10시 8 분 14 초에 네트워크를 다시 활성화했습니다.

호스트 이름을 변경하는 실제 프로세스는 다음과 같습니다. configd. 에 대한 맨 페이지 configd 그

The configd daemon is responsible for many configuration aspects of the
local system. configd maintains data reflecting the desired and current
state of the system, provides notifications to applications when this data
changes, and hosts a number of configuration agents in the form of loadable
bundles.

과

At the present time, the majority of the configuration agents (or bundles)
hosted by configd are used to establish and maintain the network
configuration.

맨 페이지는 다음과 같은 관련 파일을 나열합니다.

 /Library/Preferences/SystemConfiguration/preferences.plist
 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
 /Library/Preferences/SystemConfiguration/VirtualNetworkInterfaces.plist

파일 preferences.plist 시스템 환경 설정의 네트워크 환경 설정 패널에 지정된 네트워크 환경 설정이있는 것 같습니다. 나는 백업을 만들었고, 그것을 삭제하고, 죽였다. configd, 낮은 수준의 재부팅을 수행했습니다.

cd /Library/Preferences/SystemConfiguration/
cp preferences.plist ~/Desktop/preferences.plist
sudo rm -f preferences.plist
sudo killall configd
sudo killall configd
sudo reboot

시스템을 재부팅 한 후 시스템은 더 이상 호스트 이름을 몇 초마다 변경하지 않습니다. 아니 네트워크에 연결됩니다.

Noodling 주위에 도움이 될 수있는 수퍼 유저 스레드가 있습니다.

https://superuser.com/questions/49891/how-can-i-stop-mac-os-x-overriding-my-hostname-when-i-receive-a-dhcp-request-on

당신이 네트워크에 연결되어 있지 않을 때 이런 일이 일어나는 것은 매우 이상한 일입니다. 나는 더 나은 대답을 원합니다.

맥 환경 설정에서 DHCP 서버로부터 동적 호스트 이름을 얻을 수있는 환경 설정에 묻혀있는 환경 설정을 기억하는 것 같지만, 발견 망할 설정. 그래서 나는 잘못 기억하고 있거나 이전 키티 화신에서 나온 것이 었습니다.