FC16: 3 failures in boot.log, for which I ran the status query:
# systemctl status tcsd.service tcsd.service - LSB: Init script for TCSD Loaded: loaded (/etc/rc.d/init.d/tcsd) Active: failed since Fri, 11 May 2012 01:29:24 -0600; 6min ago Process: 961 ExecStart=/etc/rc.d/init.d/tcsd start (code=exited, status=137) CGroup: name=systemd:/system/tcsd.service
# systemctl status akmods.service akmods.service - LSB: Builds and install new kmods from akmod packages Loaded: loaded (/etc/rc.d/init.d/akmods) Active: failed since Fri, 11 May 2012 01:29:24 -0600; 7min ago Process: 962 ExecStart=/etc/rc.d/init.d/akmods start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/akmods.service
# systemctl status uuidd.service uuidd.service - LSB: UUID daemon Loaded: loaded (/etc/rc.d/init.d/uuidd) Active: failed since Fri, 11 May 2012 01:29:23 -0600; 7min ago Process: 963 ExecStart=/etc/rc.d/init.d/uuidd start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/uuidd.service
However, the query gives no clue why they failed.
On 05/11/2012 03:45 PM, JD wrote:
FC16: 3 failures in boot.log, for which I ran the status query:
# systemctl status tcsd.service tcsd.service - LSB: Init script for TCSD Loaded: loaded (/etc/rc.d/init.d/tcsd) Active: failed since Fri, 11 May 2012 01:29:24 -0600; 6min ago Process: 961 ExecStart=/etc/rc.d/init.d/tcsd start (code=exited, status=137) CGroup: name=systemd:/system/tcsd.service
If you don't have a TPM installed then the startup of tcsd will fail. What TPM do you have? If you don't have a TPM then you should either "yum erase trousers" or "systemctl disable tcsd.service"
You also could "/usr/sbin/tcsd -f" for more information as to why the daemon didn't start.
On 05/11/2012 02:55 AM, Ed Greshko wrote:
On 05/11/2012 03:45 PM, JD wrote:
FC16: 3 failures in boot.log, for which I ran the status query:
# systemctl status tcsd.service tcsd.service - LSB: Init script for TCSD Loaded: loaded (/etc/rc.d/init.d/tcsd) Active: failed since Fri, 11 May 2012 01:29:24 -0600; 6min ago Process: 961 ExecStart=/etc/rc.d/init.d/tcsd start (code=exited, status=137) CGroup: name=systemd:/system/tcsd.service
If you don't have a TPM installed then the startup of tcsd will fail. What TPM do you have? If you don't have a TPM then you should either "yum erase trousers" or "systemctl disable tcsd.service"
You also could "/usr/sbin/tcsd -f" for more information as to why the daemon didn't start.
I ran rpm -qa | grep -i tpm and got nothing.
# /usr/sbin/tcsd -f TCSD TDDL ERROR: Could not find a device to open!
The kernel I am running is the vanilla fedora 16 release kernel-3.3.4-3.fc16.i686. So, I turned tcsd off. Is this service enabled by default even though the machine has no tpm device?
Thanx for the heads up.
On 05/12/2012 02:53 PM, JD wrote:
I ran rpm -qa | grep -i tpm and got nothing.
# /usr/sbin/tcsd -f TCSD TDDL ERROR: Could not find a device to open!
The kernel I am running is the vanilla fedora 16 release kernel-3.3.4-3.fc16.i686. So, I turned tcsd off. Is this service enabled by default even though the machine has no tpm device?
Thanx for the heads up.
Well, if you install the trousers package that service is installed and defaults to on. Since you don't have any TPM hardware there is no need to have it installed. I've never have seen it installed by default on any of my systems.
So....it isn't needed. While is doesn't hard anything....you may want to remove it just to have one less unnecessary app installed.
The same goes for uuidd.
I don't know if you use akmods....but if you use that for your nvidia driver updates from rpmfusion...you may need/want it.
On 05/12/2012 12:59 AM, Ed Greshko wrote:
On 05/12/2012 02:53 PM, JD wrote:
I ran rpm -qa | grep -i tpm and got nothing.
# /usr/sbin/tcsd -f TCSD TDDL ERROR: Could not find a device to open!
The kernel I am running is the vanilla fedora 16 release kernel-3.3.4-3.fc16.i686. So, I turned tcsd off. Is this service enabled by default even though the machine has no tpm device?
Thanx for the heads up.
Well, if you install the trousers package that service is installed and defaults to on. Since you don't have any TPM hardware there is no need to have it installed. I've never have seen it installed by default on any of my systems.
So....it isn't needed. While is doesn't hard anything....you may want to remove it just to have one less unnecessary app installed.
The same goes for uuidd.
I don't know if you use akmods....but if you use that for your nvidia driver updates from rpmfusion...you may need/want it.
Unfortunately, ecryptfs-utils-96-1.fc16.i686 requires libtspi.so.1 # rpm -qv --whatprovides /usr/lib/libtspi.so.1 trousers-0.3.6-1.fc16.i686
I need to use the ecryptfs tools, which is not restricted tp tpm devices. To wit: excerpt from /usr/share/doc/ecryptfs-utils-96/README:
"In general, it is probably best to just type in your passphrase via stdin every time you need to perform a mount. Future versions of eCryptfs will allow hardware token devices, such as a TPM chip, to protect your secret keys."
On 05/12/2012 03:32 PM, JD wrote:
Unfortunately, ecryptfs-utils-96-1.fc16.i686 requires libtspi.so.1 # rpm -qv --whatprovides /usr/lib/libtspi.so.1 trousers-0.3.6-1.fc16.i686
I need to use the ecryptfs tools, which is not restricted tp tpm devices. To wit: excerpt from /usr/share/doc/ecryptfs-utils-96/README:
"In general, it is probably best to just type in your passphrase via stdin every time you need to perform a mount. Future versions of eCryptfs will allow hardware token devices, such as a TPM chip, to protect your secret keys."
I see, but you don't need the daemon.... So "systemctl disable tcsd.service" would seem to be in order.
On 05/12/2012 01:36 AM, Ed Greshko wrote:
On 05/12/2012 03:32 PM, JD wrote:
Unfortunately, ecryptfs-utils-96-1.fc16.i686 requires libtspi.so.1 # rpm -qv --whatprovides /usr/lib/libtspi.so.1 trousers-0.3.6-1.fc16.i686
I need to use the ecryptfs tools, which is not restricted tp tpm devices. To wit: excerpt from /usr/share/doc/ecryptfs-utils-96/README:
"In general, it is probably best to just type in your passphrase via stdin every time you need to perform a mount. Future versions of eCryptfs will allow hardware token devices, such as a TPM chip, to protect your secret keys."
I see, but you don't need the daemon.... So "systemctl disable tcsd.service" would seem to be in order.
Yep! Thanx Ed!