Tag Archives: FC

Safewatch Pro 2000 "FC" Code Removal

By Simonk

Hi

Problem 1:

We have a Safewatch Pro 2000 which was previously monitored by previous owners. We stopped this but now have the annoying FC displaying on Alarm Panel. Can someone advise how to clear this please?

Problem 2:

The alarm panel is upstairs (two level home) and we would like to get a remote to operate. When can we get a remote that is less expensive than the Security company would provide.

Thanks
Simon

…read more

Source: DoItYourself.com

Can't chgrp. Error – chgrp: changing group of `<file>': Invalid argument

By venmx

I found that I cannot chgrp for some reason with error:

chgrp: changing group of `’: Invalid argument

This happens on all NFS mounted disks on client machines.

We use AD (not my call) for authentication and it also provides groups.

We have a NFS server running Scientific Linux 6.3 which mounts SAN devices on FC connect. These are then exported via NFS. Clients are all CentOS 6.4.

The clients hard mounts the user’s home disk with intr,sync and various tuning options. The other disks use autofs.

AD is configured so that each user has a matching UID and GID, essentially making them the exclusive member of their own group. Not useful for sharing files unless you don’t mind making all your files accessibly by world, o+.

We need groups so that we can add members who are then able to chgrp what ever files they’d like to share with members of the same group. All seems pretty straight forward so far.

I used to run OpenLDAP with Kerberos to do all this, I had LDAP manage autofs and groups. Everything worked perfectly.

But now I cannot chgrp.

The permissions of the exported directories on the NFS server are:
drwx–x–x root root /san/home
drwxrwxrwx root root /san/otherdisks

But under home each user directory is owned by the user:
drwx–x–x user1 user1 /san/home/user1

NOTE: “other” means machines within same organization using same AD but built by other departments, “this” means the machines I built.

In the following scenarios it fails:

1. As AD user on “this” client machine on own home on “this” NFS server.
2. As AD user on “this” client machine on automounted disk on “this” NFS server.
3. As root on “this” client machine on automounted disk on “this” NFS server.

In the following scenarios it works:

1. As AD user on “this” client on local partitions where permissions allow.
2. As AD user logged in directly on “this” NFS server on any partition where permissions allow, including on SAN disks.
3. As root on “this” file server on any partition.
4. As AD user on “other” clients on export from “this” NFS server.
5. As AD user on “other” clients on export from “other” NFS server.
6. As AD user on “this” client on export from “other” NFS server.

This issue shows itself when I extract TAR files whilst on client machines to NFS exported shares as AD user or root, can’t chgrp!

I can do everything else, I can create, delete, even do newgrp and change my default group then create new files belonging to me with GID of new group. But still can’t chgrp

From: http://www.unix.com/red-hat/221091-cant-chgrp-error-chgrp-changing-group-file-invalid-argument.html

If condition matching with special chars

By ksgnathan

Hi,

I have file

Code:

#cat drivers.txt
fcs0
fcs1
vscsi1
vscsi2


In this i need to check the availabality of “fcs” or “vscsi” alone not vscsi0,fcs1

I tried with “if condition” but it is not working.

Code:

cat drivers.txt| while read ADAP
do
echo "Checking for $ADAP"
if [ $ADAP = fcs* ];then
echo "FC adapter is availabe"
fi
done


Anyone, pls advice

Source: FULL ARTICLE at The UNIX and Linux Forums