Lines in /etc/exports

[Alex_17]

Hi,

every time we make a make_net_recovery, appears a new line in /etc/exports (the same for every client). We have repeated the same line many times. Why??. Can this be avoided??.

Thanks in advance.

Alex.

[Animesh Chakraborty · Accepted solution]

Hi,
#man make_net_recovery says
".... For security reasons, it is best to export each client-specific
archive directory to just the individual client. If the recovery
archive creation is initiated from the ignite graphical user interfa
on the Ignite-UX server, and the archive server is the same as the
Ignite-UX server, the /etc/exports file will be edited automatically
so the archive can be stored in the desired location. Otherwise, if
make_net_recovery is run directly on the client the following steps
are required to be done on the archive server.
..........

[Alex_17]

Our /etc/exports file looks like (partially)

/var/opt/ignite/recovery/archives/host1 -anon=2,access=host1
/var/opt/ignite/recovery/archives/host2 -anon=2,access=host2
/var/opt/ignite/recovery/archives/host3 -anon=2,access=host3
/var/opt/ignite/recovery/archives/host4 -anon=2,access=host4
/var/opt/ignite/recovery/archives/host5 -anon=2,access=host5
/var/opt/ignite/recovery/archives/host6 -anon=2,access=host6
/var/opt/ignite/recovery/archives/host7 -anon=2,access=host7
/var/opt/ignite/recovery/archives/host8 -anon=2,access=host8
/var/opt/ignite/recovery/archives/host9 -anon=2,access=host9
/var/opt/ignite/recovery/archives/host10 -anon=2,access=host10
/var/opt/ignite/recovery/archives/host11 -anon=2,access=host11
/var/opt/ignite/recovery/archives/host1 -anon=2,access=host1
/var/opt/ignite/recovery/archives/host5 -anon=2,access=host5
/var/opt/ignite/recovery/archives/host8 -anon=2,access=host8
/var/opt/ignite/recovery/archives/host1 -anon=2,access=host1
/var/opt/ignite/recovery/archives/host10 -anon=2,access=host10
/var/opt/ignite/recovery/archives/host2 -anon=2,access=host2
/var/opt/ignite/recovery/archives/host3 -anon=2,access=host3
/var/opt/ignite/recovery/archives/host11 -anon=2,access=host11
/var/opt/ignite/recovery/archives/host4 -anon=2,access=host4
/var/opt/ignite/recovery/archives/host5 -anon=2,access=host5

The same line is repeated several times, so the file will grow and grow ...

Alex

[Steven Gillard_2]

make_net_recovery requires the archive directory to be exported on the server in order to function. Normally this is a manual step if you run the make_net_recovery command from the client but I think the GUI on the server will add a line automatically. Are you saying you are getting duplicate lines for each client, or does each line correspond to a different client system?

If you're getting duplicate lines for each client then that isn't right - sounds like a bug in Ignite. You could work around this problem by removing the duplicates and running the make_net_recovery command on each client. If each line corresponds to a different client then what you are seeing is normal behaviour and preventing it will stop Ignite from working. See the make_net_recovery man page for more information.

Regards,
Steve

[Alex_17]

Hi,

we're getting duplicated as can be seen in the file in my previous reply. I think that is wrong, but every month we have to delete some lines.

Thanks.

Alex.

[Eugen Cocalea]

Hi,

I guess Ignite doesn't check if the directory is already exported so it adds the line and exports it again.

E.

[Vincent Farrugia]

Hello,

According to the man page, published by animesh here, the /etc/exports file is edited automatically each time the Ignite session is initiated from the GUI. So I guess it does it all the time, or else I am interpreting things in a wrong way.

HTH,
Vince

[Steven Sim Kok Leong]

Hi,

The quick and dirty workaround is to write a script to remove the additional line(s) immediately after every successful run of make_net_recovery.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com

[Steven Gillard_2]

It definitely looks like Ignite is at fault here - it should check if the line already exists in /etc/exports before adding it again. If you have support with HP I would call them first to find out if it is a known problem. Otherwise you could try the latest version of Ignite if you're not running it already.

Regards,
Steve