Search Results

Those don't look that bad, but don't look relevant either.

Try to track down and kill any processes still using the share. That may allow it to finish unmounting.

If not, you may have to reboot. You'll never kill a lazy unmount. IMHO -l amounts to a...

See what's at the bottom of dmesg | less

sda1 and sda2 are on the same disk. You aren't gaining anything by putting it on sda1 vs sda2, just put it where you have lots of available space...

chattr +i would mark the file immutable meaning even root can't write to it. That would not work for a swapfile which needs to be written to.

If they're all on the same spindle anyway, none of them is really 'better'. Creating a big blank file with dd is probably the safest, no partition editing involved, unless someone decides to delete...

what did you do to fix the issue? please post so others can learn from it.





not sure what your asking.

please confirm that your using the same named.conf configuration except for the zone configuration.

does this query work while both nameservers are online?

dig +trace @192.168.2.11 unix.com a

Did you check the slave to insure it was caching the master data correctly?

please post contents of /etc/resolv.conf. ensure that both servers are listed in there.

Try it with eval, the script should be like:
#!/bin/sh

while true
do
read -p "Enter Command: " whichcmd
if [ "$whichcmd" = "end" ]
then
exit
fi
eval "$whichcmd"
done

Googling "ipv6-mcastprefix" and "ping" makes me realise that this is a common problem with Suse Linux. Finding a sensible fix amongst the sheer volume of posts is not going to be easy.

Surprised...

One side note -

You do not want accounts like oracle, root, or other major resource owners accounts locked on a production system. If you have people hacking accounts on a production system you...

From the man page of pam_tally

In my interpretation (tho I'm not sure) this means that lock_time will block access for a certain time after each failed attempt, which would be useful to slow down...