nfs, exec, group perms, etc...

QNX Newsgroups (Archives) qdn.public.qnxrtp.newuser
1

I’m seeing some strange problems and I’m wondering if it’s just me or if
someone else has seen these too.

I have 10 machines, and each one mounts /home from a Linux nfs server. The
filesystem is exported with root_squash on, but rw.

There are two peculiar problems.

A file cannot be executed unless the directory it resides in is
group-executable. Otherwise I get permission denied, even though I own the
file and the permissions are 700. (This is not the case on a local
filesystem such as /tmp).

Also, when I first log into a machine, the first time I run any executable,
I get

$ ./hello
…/hello[1]: syntax error: `(’ unexpected

but the second invocation is fine:

$ ./hello
Hello world

This seems to be the case with any executable I try in my home directory.
(Oh and hello is just a simple C program with one printf.)

Any ideas? Could it be the network card drivers? The nfs daemon? NFS
server? What can I do to help me track it down? Anything special about
group permissions I need to know?

Also, is syslogd supposed to work out of the box? I’ve started it and
nothing is appearing in /var/log/syslog (even though syslog.conf has
. /var/log/syslog in it)

I know I have a lot of work to do on my own, but I was just wondering if
someone has seen anything remotely like this.

Dana

–
Dana Echtner \ Real-Time Systems Administrator
dana@alcor.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

2

“Dana Echtner” <dana@ece.concordia.ca> wrote in message
news:94n92i$5k8$1@inn.qnx.com…

Also, is syslogd supposed to work out of the box? I’ve started it and
nothing is appearing in /var/log/syslog (even though syslog.conf has
. /var/log/syslog in it)

The things that got me were:

you have to run syslogd as root
the log file (/var/log/syslog) must already exist
there has to be a tab between the filespec and the log file in syslog.conf

Chhers
Philip

3

Philip Brown <philip.brown@cursor-system.com> wrote:

“Dana Echtner” <> dana@ece.concordia.ca> > wrote in message
news:94n92i$5k8$> 1@inn.qnx.com> …

Also, is syslogd supposed to work out of the box? I’ve started it and
nothing is appearing in /var/log/syslog (even though syslog.conf has
. /var/log/syslog in it)

The things that got me were:
you have to run syslogd as root
the log file (/var/log/syslog) must already exist
there has to be a tab between the filespec and the log file in syslog.conf

I believe that this is documented. This is because we run foremost as
an embedded system, where you don’t really want unbounded log files
growing in a constrained memory environment (though you might want the
syslog services).

Thomas

4

Dana Echtner <dana@ece.concordia.ca> wrote:

I’m seeing some strange problems and I’m wondering if it’s just me or if
someone else has seen these too.

I have 10 machines, and each one mounts /home from a Linux nfs server. The
filesystem is exported with root_squash on, but rw.

There are two peculiar problems.

A file cannot be executed unless the directory it resides in is
group-executable. Otherwise I get permission denied, even though I own the
file and the permissions are 700. (This is not the case on a local
filesystem such as /tmp).

Also, when I first log into a machine, the first time I run any executable,
I get

$ ./hello
./hello[1]: syntax error: `(’ unexpected

but the second invocation is fine:

$ ./hello
Hello world



This seems to be the case with any executable I try in my home directory.
(Oh and hello is just a simple C program with one printf.)

Please check “uname -a” to see the date of the qnx-os. If it says last year,
you have to wait for a new one.
weijie

Any ideas? Could it be the network card drivers? The nfs daemon? NFS
server? What can I do to help me track it down? Anything special about
group permissions I need to know?

Also, is syslogd supposed to work out of the box? I’ve started it and
nothing is appearing in /var/log/syslog (even though syslog.conf has
. /var/log/syslog in it)

I know I have a lot of work to do on my own, but I was just wondering if
someone has seen anything remotely like this.

Dana

–
Dana Echtner \ Real-Time Systems Administrator
dana@alcor.concordia.ca > / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

5

Thomas Fletcher wrote:

I believe that this is documented.

You’re right, it’s at the top of /etc/syslog.conf.

This is because we run foremost as
an embedded system, where you don’t really want unbounded log files
growing in a constrained memory environment (though you might want the
syslog services).

Makes sense.

–
Dana Echtner \ Real-Time Systems Administrator
dana@alcor.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

6

Philip Brown wrote:


the log file (/var/log/syslog) must already exist

Bing!

That was it, thank you!

Dana (now for some log-rotating scripts) :slight_smile:

–
Dana Echtner \ Real-Time Systems Administrator
dana@alcor.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast

7

Weijie Zhang wrote:

There are two peculiar problems.

[snip]

This seems to be the case with any executable I try in my home
directory. (Oh and hello is just a simple C program with one printf.)

Please check “uname -a” to see the date of the qnx-os. If it says last
year, you have to wait for a new one.

QNX askja 6.00 2000/09/13-14:09:41edt x86pc x86

It’s last year.

So what you’re saying is that patch A might help me?

D.

8

Dana Echtner wrote:


So what you’re saying is that patch A might help me?

It didn’t. :frowning:

Is this a known bug, or is it something I’m doing?

Dana

–
Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada

rw-rw-rw-: The file protection of the beast