Prev: unixODBC
Next: Commit the applied FixPak??
From: Darin McBride on 21 Mar 2007 00:01 Ray wrote: > On Mar 20, 11:02 am, "Harlin" <harlinser...(a)yahoo.com> wrote: >> How would I use dasupdt to restore permissions if no das user exists? > >> DBI1082E The file or directory /home/dasusr1/das already exists. > According to that, the das user DOES exist. Actually, that merely means it *probably* exists. Using daslist is a bit more definitive (as it uses the same API that DB2 uses internally to figure out the das). The combination of the output from daslist *and* the das directory both existing is pretty much definitive.
From: Ray on 21 Mar 2007 12:06 On Mar 20, 11:01 pm, Darin McBride <dmcbr...(a)tower.to.org.no.spam.for.me> wrote: > Ray wrote: > > On Mar 20, 11:02 am, "Harlin" <harlinser...(a)yahoo.com> wrote: > >> How would I use dasupdt to restore permissions if no das user exists? > > >> DBI1082E The file or directory /home/dasusr1/das already exists. > > According to that, the das user DOES exist. > > Actually, that merely means it *probably* exists. Using daslist is a bit > more definitive (as it uses the same API that DB2 uses internally to figure > out the das). The combination of the output from daslist *and* the das > directory both existing is pretty much definitive. Are we talking about the das or the das USER (dasusr1 in this case)? I guess dasusr1 could have been removed from the system leaving his home directory intact. Is that the scenario?
From: Darin McBride on 21 Mar 2007 13:31 Ray wrote: > On Mar 20, 11:01 pm, Darin McBride > <dmcbr...(a)tower.to.org.no.spam.for.me> wrote: >> Ray wrote: >> > On Mar 20, 11:02 am, "Harlin" <harlinser...(a)yahoo.com> wrote: >> >> How would I use dasupdt to restore permissions if no das user exists? >> >> >> DBI1082E The file or directory /home/dasusr1/das already exists. >> > According to that, the das user DOES exist. >> >> Actually, that merely means it *probably* exists. Using daslist is a bit >> more definitive (as it uses the same API that DB2 uses internally to >> figure >> out the das). The combination of the output from daslist *and* the das >> directory both existing is pretty much definitive. > > Are we talking about the das or the das USER (dasusr1 in this case)? I > guess dasusr1 could have been removed from the system leaving his home > directory intact. Is that the scenario? No - that's another scenario altogether ;-) Some users go and just delete the das directory without using dasdrop - and then you end up with daslist showing the das existing, but the das code is gone. Some users end up with a das directory without a das listing in a number of ways: the directory that the das list is stored in is marked read-only, so it fails to be updated; the das directory gets restored from backup after it was dropped; the das directory is mounted from another machine (e.g., a shared /home where stuff gets shared that doesn't need to be shared). There are probably more possibilities. In your case, where the das user is deleted, but the home directory wasn't removed, attempting to get information on the das user (to find the home directory) will fail. I'm not sure if daslist will detect this (probably not), but trying to do a directory of ~dasusr1/das will fail (since the shell can't find the user 'dasusr1').
From: Ray on 21 Mar 2007 17:06
On Mar 21, 12:31 pm, Darin McBride <dmcbr...(a)tower.to.org.no.spam.for.me> wrote: > No - that's another scenario altogether ;-) Great. I was afraid I was misunderestimating my ability to understand the root of the problem. |