> Yeah no luck here either. I didn't think permissions on sysfs were > persistent across reboots, but you could try chmod'ing that directory and > file, and see if you can access it after the system boots up. > > Also, one of the few things I found was that the initscripts don't like > when max_bonds is set to 0, so check your modprobe.conf for that.
Actually, i just setup a bond on my centos5.2 system, and I don't even see that file in that sysfs directory: # ll /sys/class/net/bond0/bonding/ total 0 -rw-r--r-- 1 root root 4096 Jun 2 06:42 active_slave -r--r--r-- 1 root root 4096 Jun 2 06:42 ad_actor_key -r--r--r-- 1 root root 4096 Jun 2 06:42 ad_aggregator -r--r--r-- 1 root root 4096 Jun 2 06:42 ad_num_ports -r--r--r-- 1 root root 4096 Jun 2 06:42 ad_partner_key -r--r--r-- 1 root root 4096 Jun 2 06:42 ad_partner_mac -rw-r--r-- 1 root root 4096 Jun 2 06:42 arp_interval -rw-r--r-- 1 root root 4096 Jun 2 06:42 arp_ip_target -rw-r--r-- 1 root root 4096 Jun 2 06:42 arp_validate -rw-r--r-- 1 root root 4096 Jun 2 06:42 downdelay -rw-r--r-- 1 root root 4096 Jun 2 06:42 fail_over_mac -rw-r--r-- 1 root root 4096 Jun 2 06:42 lacp_rate -rw-r--r-- 1 root root 4096 Jun 2 06:42 miimon -r--r--r-- 1 root root 4096 Jun 2 06:42 mii_status -rw-r--r-- 1 root root 4096 Jun 2 06:42 mode -rw-r--r-- 1 root root 4096 Jun 2 06:42 primary -rw-r--r-- 1 root root 4096 Jun 2 06:42 slaves -rw-r--r-- 1 root root 4096 Jun 2 06:42 updelay -rw-r--r-- 1 root root 4096 Jun 2 06:42 use_carrier -rw-r--r-- 1 root root 4096 Jun 2 06:42 xmit_hash_policy Could be a bug in the initscripts? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
