Mailinglist Archive: opensuse (4054 mails)
| < Previous | Next > |
Re: [SLE] What is so special on /dev/hda? was how to make device permissions stick?
- From: Peter Sutter <sutterp@xxxxxxxxxxxx>
- Date: Wed, 18 Jan 2006 10:04:44 +0800
- Message-id: <200601181004.44891.sutterp@xxxxxxxxxxxx>
On Tuesday 17 January 2006 23:28, Sunny wrote:
> On 1/16/06, Peter Sutter <sutterp@xxxxxxxxxxxx> wrote:
> > Thanks, Sunny
> >
> > The burning runs under wwwrun. Assigning a group does not
> > help, because the file re-sets to
> > brw------- 1 root disk 3, 0 Oct 2, 2004 /dev/hda
> > which does not give write access to the group, only to the
> > owner.
> >
> > Peter
>
> Hi Peter,
> from your answer I did not understand:
>
> Did you run k3bsetup program? Did you enabled "Using a burning
> group"? This should change the device permission to brw-rw--- for
> the group given in the setup. Then just add wwwrun user to this
> group.
>
> --
> --
> Svetoslav Milenov (Sunny)
Thanks Sunny,
The machine the apache web server is running on does not have a
graphical user interface. It is a server, nobody logs on to it
interactively, except the system administrator fromtime to time.
There is no kde or k3bsetup.
The web page prompts for a directory, the files in this directory
are then uploaded to the server and then burned to dvd.
The image is created with mkisofs, for the burning of the image to
dvd growisofs is used.
To burn the dvd, growisofs needs physical access to the dvd burner,
which is /dev/hda, and the permissions of /dev/hda change from 666
root:disks to 600 root:disks after a crash.
We have a very unreliable power supply in the area with frequent
power cuts and one of these older UPS with no interface to control
it. So the system often crashes because of no power. When the
system restarts when the power returns, /dev/hda has always a
permission of 600 with owner root:disks, which is not enough for
wwwrun:root to access the device.
Something in the startup sets the permission back to 600 root:disks.
Running SuSEconfig manually after a crash fixes the problem. If I
know which script changes the permissions back to 600 root:disks, I
could change it there, without having to run SuSEconfig manually.
The strange thing is, that other devices keep their settings, it
seems it is just the IDE drives /dev/hda that keeps changing, SATA
and USB drives /dev/sda, /dev/sdb keep their settings after a
re-boot. The boot/root partitions are on a SATA drive /dev/sda.
Peter
> On 1/16/06, Peter Sutter <sutterp@xxxxxxxxxxxx> wrote:
> > Thanks, Sunny
> >
> > The burning runs under wwwrun. Assigning a group does not
> > help, because the file re-sets to
> > brw------- 1 root disk 3, 0 Oct 2, 2004 /dev/hda
> > which does not give write access to the group, only to the
> > owner.
> >
> > Peter
>
> Hi Peter,
> from your answer I did not understand:
>
> Did you run k3bsetup program? Did you enabled "Using a burning
> group"? This should change the device permission to brw-rw--- for
> the group given in the setup. Then just add wwwrun user to this
> group.
>
> --
> --
> Svetoslav Milenov (Sunny)
Thanks Sunny,
The machine the apache web server is running on does not have a
graphical user interface. It is a server, nobody logs on to it
interactively, except the system administrator fromtime to time.
There is no kde or k3bsetup.
The web page prompts for a directory, the files in this directory
are then uploaded to the server and then burned to dvd.
The image is created with mkisofs, for the burning of the image to
dvd growisofs is used.
To burn the dvd, growisofs needs physical access to the dvd burner,
which is /dev/hda, and the permissions of /dev/hda change from 666
root:disks to 600 root:disks after a crash.
We have a very unreliable power supply in the area with frequent
power cuts and one of these older UPS with no interface to control
it. So the system often crashes because of no power. When the
system restarts when the power returns, /dev/hda has always a
permission of 600 with owner root:disks, which is not enough for
wwwrun:root to access the device.
Something in the startup sets the permission back to 600 root:disks.
Running SuSEconfig manually after a crash fixes the problem. If I
know which script changes the permissions back to 600 root:disks, I
could change it there, without having to run SuSEconfig manually.
The strange thing is, that other devices keep their settings, it
seems it is just the IDE drives /dev/hda that keeps changing, SATA
and USB drives /dev/sda, /dev/sdb keep their settings after a
re-boot. The boot/root partitions are on a SATA drive /dev/sda.
Peter
| < Previous | Next > |