Mailinglist Archive: opensuse (4054 mails)

[Randall R Schulz <rschulz@xxxxxxxxx>]

Peter,

On Wednesday 18 January 2006 06:45, Peter Sutter wrote:
> ...
>
> Thanks Randall,
>
> rpm -v resmgr reported
> .......T c /etc/resmgr.conf
> which I interpret as all OK.

I don't know why. Here's an excerpt from the man page you could have
read to avoid guessing:

% man rpm
  ...
  The format of the output is a string of 8 characters, a possible
  attribute marker:

  c %config configuration file.
  d %doc documentation file.
  g %ghost file (i.e. the file contents are not included in the package payload).
  l %license license file.
  r %readme readme file.

  from the package header, followed by the file name. Each of the 8
  characters denotes the result of a comparison of attribute(s) of the
  file to the value of those attribute(s) recorded in the database. A
  single "." (period) means the test passed, while a single "?" (question
  mark) indicates the test could not be performed (e.g. file permissions
  prevent reading). Otherwise, the (mnemonically emBoldened) character
  denotes failure of the corresponding --verify test:

  S file Size differs
  M Mode differs (includes permissions and file type)
  5 MD5 sum differs
  D Device major/minor number mis-match
  L readLink(2) path mis-match
  U User ownership differs
  G Group ownership differs
  T mTime differs
 ...


The output you got means that /etc/resmgr.conf was touched (its
modification time changed), though its content was not.


> I removed resmgr, installed it again and then run an online update.
> This seems to have fixed the problem, at least partially, in that I
> get a meaningful response now. So it appears that resmgr was
> broken.

The diagnostic you were getting from the RPM verification was not about
a config file, so whatever the problem, it was not in the resmgr
package's files themselves, but if the reinstallation fixed the problem,
then great.


> # resmgr list
> status code 200
> server message follows:
> no devices available
>
> resmgr seems to dislike ssh connections.

% man pam_resmgr


% resmgr list
r--- /dev/console
rw-- /dev/adsp
rw-- /dev/audio
rw-- /dev/dsp
rw-- /dev/mixer
rw-- /dev/snd/controlC0
rw-- /dev/snd/pcmC0D0c
rw-- /dev/snd/pcmC0D0p
rw-- /dev/snd/pcmC0D1p
rw-- /dev/snd/pcmC0D2p
rw-- /dev/snd/pcmC0D3p
rw-- /dev/midi
rw-- /dev/snd/midiC0D0
rw-- /dev/snd/seq
rw-- /dev/snd/timer
rw-- /dev/input/event2
rw-- usb:bus=3,dev=2
rw-- /dev/hdc
rw-- /dev/hda
rw-- /dev/fd0


> So I may have to physically 
> visit the system to test it out further. I tried this on a test
> system here, I get access to resmgr when logged in on a console or
> via kde, but not via ssh.

The "list" verb does not require root privilege, by the way.


> btw, would you know where I can find a description of the resmgr
> status codes?

% man resmgrd


> ...
> Peter

I hope you see the pattern in my answers.


Perhaps you'd be willing to dispense with the "Reply-To" header in your
posts to this list?


Randall Schulz