On 14 October 2014 17:12, Ian Collins via smartos-discuss < [email protected]> wrote:
> Keith Wesolowski wrote: > >> Best is subjective. Here are some options: >> > >> 1. Build a new platform. >> >> 2. Replace /etc/system via boot-time modules. >> >> 3. Use mdb, possibly via a custom service that runs at boot. It's >> possible that for some applications this might be too late. >> >> 4. Use kmdb early in boot. >> >> 5. Fix illumos. >> >> As I feared... > > From the above, it looks like a moving from a Solaris to a SmartOS zone > was a bad choice for a Samba server. The prospect of building a Linux > KVM to work around the ngroups_max problem fills me with dread. I'd > better take a tin hat when I tell my client.... > The email at https://www.mail-archive.com/[email protected]/msg01010.html describes how to do #2 when booting via USB. #3 looks pretty easy if you are running Samba in a zone because zones will come up late (last?) in the boot process. #5 shouldn't be too hard either, but I doubt it will meet your timeframes. If you are PXE booting your boxes you may be able patch the boot archive. It seems to be a Solaris file system, so you should be able to just mount it via lofi(7D) and then simply edit /etc/system like a normal file. If you are feeling especially keen, you could just patch the boot archive with a binary editor. The data in /etc/system file is extensive and easy to find. I don't know if PXE booting uses the boot_archive.hash file, but it's the SHA1 hash of the boot archive, so calculating the new hash won't be hard. Cheers, Lloyd ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
