# Realport not restoring correct linux tty port permissions on power cycle **URL:** \ **Category:** Realport\ **Created:** [May 13, 2008, 9:55pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093 "2008-05-13T21:55:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rich\_at\_mbari.org](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@rich\_at\_mbari.org](https://forums.digi.com/u/rich_at_mbari.org)\ **Post date:** [May 13, 2008, 9:55pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093/1 "2008-05-13T21:55:10Z")
Realport or my Digi SP One on RedHat-5 seems to ignore the dgrp\_gui settings if the power is cut/restored to the SP One device. (power availability at the device is beyond my control). The /dev/ttyaa00 port owner and group are reset to root and mode is reset to 600. Ive checked the /etc/dgrp.backing.store file after setting the owner & group ids and access=666 using the dgrp\_gui. Ive even tried editing the init.d/dgrp\_daemon script file to force owner, group and access mode. The device always re-powers up and resets the /dev/ttyaa00 from: crw-rw---- 1 root uucp to: crw------\_\_1 root root How can I force Realport or dgrp\_demon or the device to restore the desired permissions? my config… Red Hat Enterprise Ed. 5 4002086\_n.src.rpm dgrp-1.9-17.i386 Digi One SP ---
**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\ **Post date:** [May 14, 2008, 2:25pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093/2 "2008-05-14T14:25:07Z")
I believe that distribution version utilizes UDEV. If so, UDEV controls the device permissions. The following thread should be helpful: [http://www.digi.com/support/forum/viewthread\_thread,4407#13674](http://www.digi.com/support/forum/viewthread_thread,4407#13674) ---
**Author:** ![rich\_at\_mbari.org](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@rich\_at\_mbari.org](https://forums.digi.com/u/rich_at_mbari.org)\ **Post date:** [May 14, 2008, 4:03pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093/3 "2008-05-14T16:03:31Z")
That fixes my problem. Thanks for the great help! -Rich ---
**Author:** ![rich\_at\_mbari.org](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@rich\_at\_mbari.org](https://forums.digi.com/u/rich_at_mbari.org)\ **Post date:** [May 14, 2008, 4:41pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093/4 "2008-05-14T16:41:17Z")
Follow-up question. For these systems that use UDEV then, are all of the documentation references to the dgrp\_gui and dgrp\_deamon start/stop/settings irrelevant or do they have some effects that need to be considered in my final configuration also? ---
**Author:** ![userid0](https://avatars.discourse-cdn.com/v4/letter/u/f6c823/32.png) [@userid0](https://forums.digi.com/u/userid0)\ **Post date:** [May 29, 2008, 3:10pm UTC](https://forums.digi.com/t/realport-not-restoring-correct-linux-tty-port-permissions-on-power-cycle/7093/5 "2008-05-29T15:10:23Z")
Sorry, just noticed your follow up question. Yes, dgrp\_gui and the daemon settings with regards to port ownership/permissions are irrelevant if UDEV is used. UDEV actually creates the devices (not the Digi driver daemon) and uses its rules to define the settings when they are created. The Digi driver rules/settings are ignored.