Custom Query (15 matches)
Results (10 - 12 of 15)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | replace getopt function by OptionParser | somebody | bas |
| Description |
Is much simpler |
|||
| #7 | invalid | PXE_CONF_DIR should be configurable | somebody | ramonb@… |
| Description |
The 'PXE_CONF_DIR' path (/tftpboot/pxelinux.cfg) is now hardcoded in the pxeconfig utility. Could this be made configurable? Perhaps through a configfile. install.gina.sara.nl:/data/cfengine/data root# apt-show-versions | grep pxeconfig pxeconfig/etch uptodate 2.0.0-1 install.gina.sara.nl:/data/cfengine/data root# grep ^PXE_CONF_DIR `which pxeconfig` PXE_CONF_DIR='/tftpboot/pxelinux.cfg' install.gina.sara.nl:/data/cfengine/data root# Our pxelinux.cfg is in a alternate location (/data/tftpboot/pxelinux.cfg) and we now have to manually edit the pxeconfig utility after each upgrade. |
|||
| #6 | fixed | Adding pading character | bas | bas |
| Description |
Hi Bas, I'm about to add 50 new servers to our cluster, and I came across a minor bug in pxeconfig. The new nodes will be q089...q138, but how do I specify this with pxeconfig ? The obvious way is to use 3-digit start and end numbers, but pxeconfig doesn't like that: # pxeconfig --basename q -s 089 -e 138 -f default.memdisk_x3455_broadcom_fw_204 q89 not an valid hostname: (-2, 'Name or service not known') The workaround is to split the range into 89..99 and 100..138. But perhaps pxeconfig could be modified into using 3 digits is I specify the numbers with 3 digits ? Thanks a lot, Ole |
|||
