Keep running into this problem. Getting cron failures in /var/cron/log:
someuser 4151 c Mon Feb 29 12:35:00 1993
! bad user (someuser) Mon Feb 29 12:35:00 1993
Inevitably, the user has locked themselves (or a malicious someone) out of the server.
Check /etc/shadow for *LK* on the user.
passwd -u someuser to unlock.
When building Solaris 10 servers in bulk.. That is 1 or more at a time. I usually don’t enable any sort of name resolution until later.
That’s the problem. When later rolls around, I’ve forgotten that I hadn’t enabled anything.
This would be fine and dandy if nslookup or host would let me know that my /etc/nsswitch.conf is only looking at files. It ignores that and goes strictly with what is in /etc/resolv.conf seemingly. So if that’s broke or incorrect it will, at least, tell you that.
I seem to be searching and using the same google result a bunch lately. So here it is:
Changing the IP on Solaris 10 requires editing two files:
3. /etc/netmasks (if subnet mask needs changing)
If you are changing network address, you will need to change the router address in the file:
Changing the hostname now only requires editing these files:
3. /etc/hostname.”interface name”
hostname “hostname” (change until you can reboot)
Thanks to shiv729 at devshed.
Original forum post:
bash-3.00# zoneadm list -iv
ID NAME STATUS PATH
0 global running /
11 foo running /export/zones/foo
13 bar running /export/zones/bar
bash-3.00# zonecfg -z fubar
fubar: No such zone configured
Use ‘create’ to begin configuring a new zone.
zonecfg:fubar> set zonepath=/export/zones/fubar
zonecfg:fubar> set autoboot=true
zonecfg:fubar> add net
zonecfg:fubar:net> set physical=eth0
zonecfg:fubar:net> set address=192.168.1.1
zonecfg:fubar> add attr
zonecfg:fubar:attr> set name=comment
zonecfg:fubar:attr> set type=string
zonecfg:fubar:attr> set value=”FOOBED”
bash-3.00# zoneadm -z fubar install
This is the first part in a series of notes taken regarding new(ish) Solaris 10 technologies. Other items I have notes on are ZFS and new service administration.
Zones, Containers, Domains and Partition (According to Sun):
Zone: chroot’d virtual machine. Some resources are shared, for example, the kernel or /usr/lib.
More info below.
Container: Zone with resource controls in place. At this time, limited to number of CPUs.
See “Resource Pools”
Domain: Grouping of hardware in enterprise class Sun servers
Partition: Segregation of domain grouped hardware.