That is truthfully not the right way to handle this. Proper way is to use a mail client that has proper support for mailing lists (like the reply-to list extension for a suitably patched Thunderbird).
There are arguments about this on probably all internet lists. ...... Original Message ....... On Fri, 28 Mar 2008 12:35:03 -0400 "Rodney Morris" <[EMAIL PROTECTED]> wrote: >On 3/28/08, Jue Yang <[EMAIL PROTECTED]> wrote: > > > > hi, > > > > I am now in trouble. Could anybody can tell me what causes the error as > > follows. > > > > > >> Mar 29 15:13:42 localhost dhclient: Can't create > > /usr/local/var/run/dhclient-wlan0.pid: Permission denied > > Mar 29 15:13:42 localhost dhclient: Internet Systems Consortium DHCP Client > > V3.0.6-Fedora > > Mar 29 15:13:42 localhost dhclient: Copyright 2004-2007 Internet Systems > > Consortium. > > Mar 29 15:13:42 localhost dhclient: All rights reserved. > > Mar 29 15:13:42 localhost dhclient: For info, please visit > > http://www.isc.org/sw/dhcp/ > > Mar 29 15:13:42 localhost dhclient: > > Mar 29 15:13:42 localhost dhclient: can't create > > /usr/local/var/run/dhclient-wlan0.lease: Permission denied > > Mar 29 15:13:42 localhost dhclient: execve > > (/usr/local/libexec/nm-dhcp-client.action, ...): Permission denied > > Mar 29 15:13:42 localhost dhclient: Listening on LPF/wlan0/00:18:e7:20:a5:fb > > Mar 29 15:13:42 localhost dhclient: Sending on LPF/wlan0/00:18:e7:20:a5:fb > > Mar 29 15:13:42 localhost dhclient: Sending on Socket/fallback > > Mar 29 15:13:42 localhost dhclient: Can't create > > /usr/local/var/run/dhclient-wlan0.pid: Permission denied > > Mar 29 15:13:42 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 > > port 67 interval 5 > > Mar 29 15:13:42 localhost dhclient: DHCPOFFER from 192.168.1.1 > > Mar 29 15:13:42 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 > > port 67 > > Mar 29 15:13:42 localhost dhclient: DHCPACK from 192.168.1.1 > > Mar 29 15:13:42 localhost dhclient: execve > > (/usr/local/libexec/nm-dhcp-client.action, ...): Permission denied > > Mar 29 15:13:42 localhost dhclient: can't create > > /usr/local/var/run/dhclient-wlan0.lease: Permission denied > > Mar 29 15:13:42 localhost dhclient: bound to 192.168.1.101 -- renewal in > > 35376 seconds. > > Mar 29 15:13:42 localhost dhclient: Can't create > > /usr/local/var/run/dhclient-wlan0.pid: Permission denied > > Mar 29 15:13:43 localhost avahi-daemon[2443]: Registering new address record > > >... > > > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing > > /sbin/dhclient (dhcpc_t) "write" to <Unknown> (usr_t).#012 For complete > > SELinux messages. run sealert -l > > b88bcdd9-3df7-4ff1-8b4b-3f42b0ad1c4f > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing the > > dhclient (dhcpc_t) from executing <Unknown>.#012 For complete SELinux > > messages. run sealert -l > > a13b090e-265b-41a3-a988-7fdde73fdf53 > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing > > /sbin/dhclient (dhcpc_t) "write" to <Unknown> (usr_t).#012 For complete > > SELinux messages. run sealert -l > > b88bcdd9-3df7-4ff1-8b4b-3f42b0ad1c4f > > Mar 29 15:13:44 localhost kernel: Linking with orap_abc > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing > > /sbin/dhclient (dhcpc_t) "write" to <Unknown> (usr_t).#012 For complete > > SELinux messages. run sealert -l > > b88bcdd9-3df7-4ff1-8b4b-3f42b0ad1c4f > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing the > > /sbin/dhclient (dhcpc_t) from executing <Unknown>.#012 For complete > > SELinux messages. run sealert -l > > a13b090e-265b-41a3-a988-7fdde73fdf53 > > Mar 29 15:13:44 localhost setroubleshoot: #012 SELinux is preventing > > dhclient (dhcpc_t) "write" to <Unknown> (usr_t).#012 For complete > > SELinux messages. run sealert -l > > b88bcdd9-3df7-4ff1-8b4b-3f42b0ad1c4f > > >Is SElinux set to enforcing? If so, try setting SElinux to permissive > mode. Looking at the logs, SELinux may be preventing dhclient from > creating pid and lease files, though I'm no SELinux expert. > > Rod > >Ugh! I forgot to include the list in the above reply. Could someone >set the reply-to to the list on all messages? >_______________________________________________ >NetworkManager-list mailing list >[email protected] >http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
