Hi, I'm trying to setup my new APC ups on ttyS0. ttyS0 is working as I would expect. APC's instructions say to set /dev/ttyS0 to the user created to run their program. Ok, no biggy. Except that ttyS0's owner/group keep getting reset back to root:root.

Can someone tell me how to keep the owner group settings I put there?

Since I'm running 2.4, udev isn't usable. So where in the heck is this getting reset? Obviously in Slack, /etc/inittab respawns the device, but what am I missing?

/etc/inittab...
s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100

Slackware 10.2
ext2
kernel 2.4.31
/dev/ttyS0

What else might you want to know?

Thanks for any help...
John

You could just grep through the init scripts:

grep /dev/tty /etc/init.d/*

on Debian. Maybe /etc/rc.d on slack? I see some chmod/chown getting done.

interesting.... are you sure you need getty for this? i haven't used apc ups on linux b4, as i use a belkin. i'm no expert on this, but it seems the process just opens /dev/ttyS0. for me, the ttyS0 line in inittab is commented out.

Thanks for the suggestion, and I've already done that. On slackware there isn't a /etc/init.d/ However there are plenty of startup files and all I find are references to the boot time. But the problem happens while its running, so the bootup scripts can't be at fault.

Thanks
John

No not entirely sure. 'agetty' wasn't discussed in the APC install manual. But it was enabled after the OS install. Could 'agetty' be resetting the permissions? I don't see anything in the /etc/inittab which would set perms. But if there was some default of root:root, and agetty re-makes the device upone some unknown criteria, then perhaps thats when it happens. It's obvious that agetty gets 'respawned', but I don't know when or why.

Thanks
John