i am having a strange problam. i upgraded the porting set. from 05.04 to 06.04 some days back and now when i am generating any new session through user root. it is not getting executed by any other user.it is giving error object not found. the users r in bsp group in unix and the root in sys group. but earlier this was not the case. the reports were working fine irrespactive of their owener user. i checked, the owner and group of the new objects and new reports are root and sys respectivly while earlier it was root and bsp.
wot can b the possible reason for this. and how can it b solved....
any suggestion...

Run session as normal other user with:
-- -dbgfdev -keeplog -logfile DiskAccess <own session code>
in the file DiskAccess you can see if the normal user gets error 13 (permission problem on disk files) or not.

If not, then did you convert the session to RDD (ttadv5210m000)
Did you make the new session (in a new module) so that in the $BSE/application there are files (or directories) with ownership root?
ls -altrR ${BSE}/application/* | grep root
If so you should run the command
chown -R bsp:bsp ${BSE}/application/*

To be honest: Do not look for a solution. Change your working behaviour.

The usage of unix user root is not recommended for Baan.
If you generate logs and Baan starts a new logfile with this user,
then this will also belong to root and the next user can not write it and so on.

Just don't do it.

Oh I definitly agree on that. User root is for OS system maintenance only.

But what I meant was to make it visible where what things go wrong if you do things like that. Within Baan user root equals permission problems. Once you understand what goes wrong and why, you will not do it again. Once you have been told, you still must have trust in the one who tells you.

In my practice as a father I learned that it is only of little use to just forbid things. When you explain why they are not allowed to do things, they will tend to be more obedient.

There may also be other things except for permission issues, but I addressed that too, I think.

Doing stuff in Baan as user 'root' is bad bad bad. You should only use the 'root' account for two things:
starting/stopping Baan
(re)-License Baan

Any other tasks should be performed by either the generic super user 'bsp' or as any other user.

A consistent working practice will not get you into file permission problems as you have now.

hi
I got ur point and thanx for valuable suggestions. i have changed my working attitude. now i work through bsp. but i still unable to understand y is it happening so. earlier when i used to work with user root it work was visible to every user. now when i work with user root the files created by root are not having permission to other groups.(only to creater and group). and root is of sys group so any user from bsp group cannot execute any of the object created by root. y is it so...

Originally posted by GAURAVGUPTA9
hi
I got ur point and thanx for valuable suggestions. i have changed my working attitude. now i work through bsp. but i still unable to understand y is it happening so. earlier when i used to work with user root it work was visible to every user. now when i work with user root the files created by root are not having permission to other groups.(only to creater and group). and root is of sys group so any user from bsp group cannot execute any of the object created by root. y is it so...

Have you changed the umask for user 'root'?

wot is this umask of root. i didn't change that.

Gaurav,

I suggest you do some research on what the 'umask' is and how it affects file permissions. Here's a good pointer:

http://unix.about.com/library/glossary/bldef-cmd-umask.htm

You might want to check to see if the default permissions set for root allows read access by other groups. This default is set by Unix and can be changed by using the umask command, but if you ever do a switch user (su command) to root without reading root's .profile (su vrs su -), the system default permissions for root
will be used.

Good Luck

GAURAVGUPTA9:... But I am still unable to understand why is it happening so. earlier when i used to work with user root it work was visible to every user...
OmeLuuk:... Did you make the new session (in a new module) so that in the $BSE/application there are files (or directories) with ownership root?...(see above)
It could be that your session started in a new module (or even package) that caused a new directory to be made in the $BSE/application that had root permission where the objects themselves are bsp:bsp readable?