make use of your IVE ports for this kind of stuff, get a cable run to an IVE port and split it up amongst your VIOS for maintenance access.
my 2 cents.
and as a final post to this misplaced thread, we found the root cause. I'll post it here because it turns out to affect linux just as easily as AIX(both normally disallow this behavior and many others I suspect also normally only allow root to chown)
on one of the netapp filers we had an option...
and oops. after reading the SElinux post with some confusion i realized i posted this to the wrong forum. i meant to post it in AIX. :D
ah well, i don't see any way to move it.
directories, ownership, permissions don't appear to make any difference.
at this point i've got a call open with ibm and after some traces they believe somehow the netapp filer is allowing this... although still investigating. i had kind of figured this would be more of an OS control...
I have a weird one and at this point i'm not sure if its a bug or a feature.
i have two NFS mountpoints from two different Netapp filers.
on one netapp filer mountpoint, a user who owns the mountpount directory may create a file in the mountpoint and then chown that file to any other...
so i've never done this in linux and i might be misunderstanding your question but here's the way i read it:
your network guy is suggesting that you run the LLT/GAB VLAN traffic over the same physical NIC for production traffic. basically doubling up those ports. not a bad idea since LLT/GAB is...
aha, thanks.. i reversed the use but same difference.. this way i can keep $port as the global and have a new var just for the one offs inside the loop.
while read server nport; do
echo "devcreate ${server%%.*} $server ${nport:-$port}"
done < $file
...global value of $port in the loop?
#!/bin/bash
export port=161
export file=~/test1
while read server port; do
echo "devcreate ${server%%.*} $server $port"
done < $file
contents of test1:
fqdn1.hostname.com
fqdn2.hostname.com
fqdn3.hostname.com 4161
fqdn4.hostname.com 161...
you probably need to expect the prompt and then send your command
one question though, do you have to use telnet for this? it'd be much easier to accomplish with ssh if the servers support them as you can run non-interactive sessions through ssh and with keys.. no need for password prompting...
monitoring their shell history file(s) as Annihilannic said is the most simplistic way.. lots of caveats there.
one way to "watch" real time another persons terminal is for them to use GNU Screen, you can then attach to their session. google has a lot more detail on how to use screen.
without...
...on the linux kernel.
i'm sure over the years there have been ideas picked up by one or the other for use in their own design but thats about it.
sjm2 describes it pretty well, the kernel is a component of AIX, its just the middleman between the software stack and the hardware on any *nix OS.
just as an fyi, i have a little function in my .profile that does the same thing, only pretty. :)
might find it handy to add if you're in an environment like me with many hmc's.
[3896][xxxxxx]:/home/jeffq> lshmc
xxxx.com is 10.xxx.xxx.65
xxxx.com is 10.xxx.xxx.66
[3897][xxxxxxx]:/home/jeffq>...
guess im a little fuzzy on your requirements but if you just want to see if a file contains a string and do something if it does then simply:
grep <string> <file> && <command>
I have a user who needs to change which group files get written out as several times within a script.
at first we looked at using setgroups and newgrp but those spawn a new shell and thus break the script.
i know at the end of the day we can just do a chgrp as a second operation for whatever...
just wanted to echo others comments,
from reading your post i think your best bet would be to install virtualbox on an existing system and load up some Linux VM's to play with... my recommendations would be:
1. CentOS5(this is quite literally RedHat enterprise or RHEL with the branding...
I'm curious, over the past week i've been playing with xCAT 2.2 to centrally manage our linux/aix servers.. on the aix side of the house it was a breeze, after digging around and finding the right combo of doc's it all came together pretty quick and i've got both software and hardware control...
been years since i did anything with sendmail but normally it writes the emails to /var/spool/mqueue unless you've explicitly set it differently in sendmail.cf like:
# queue directory
O QueueDirectory=/var/spool/mqueue
at least if i were getting this error that'd be the first place i look.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.