New answers tagged

0

This is happening not only for LD_LIBRARY_PATH but a few other environment variables that could temper with your build environment. In my case, sudo has become: sudo -HE env PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} PYTHONPATH=${PYTHONPATH} my_command


0

The ownership of the terminal device is not changed when using sudo, but changing its permissions is actually not the only solution (not a great solution though, because it opens a security hole). The common approach is to start a "script" session (but don't save the output, send it to the trash), which works because it uses another terminal device. sudo -...


0

try running fdisk -l just to make sure /def/sdf is the actual block name, so probably it should mount with: sudo mount /dev/sdf1 /vol-a


0

How are you maintaining the time on your server. If you have a poorly running clock, then the time may need to be jumped periodically. This may cause sudo to notice future timestamps and try to fix them. However, I would expect different message. If you are using ntp with poor conectivity or a large step setting time may jump far enough that sudo would ...


0

I would recommend you to backup the MBR too with dd, to restore after your disk cloning process, rewriting the partition table ( just to make sure ). Copy the MBR : ~# dd if=<SOURCE_DISK> of=/path/to/mbr_file.img bs=512 count=1 Restore the partition table : ~# dd if=/path/to/mbr_file.img of=<DESTINATION_DISK> bs=1 skip=446 count=64 However,...


1

If you did this sudo dd if=/dev/sda1 of=/dev/sdc1 and your data really was on sda1 then your data should still be safe on sda1. Anything else and all bets are off.


0

I had this problem on a RH Like custom system, the file /etc/pam.d/sudo didn't exists. I just link it to /etc/pam.d/system-auth and it works: root@fws1:~ # ln -s /etc/pam.d/system-auth /etc/pam.d/sudo


0

I would suggest to either set the ignore_group_members option to true, or symlink the cache to tmpfs or wait for the 1.14 upstream release. The reason the group resolution is slow is that saving the group on cache update after the cache expiration always writes the full group object to the on-disk cache even if nothing had changed. In 1.14, we're changing ...


0

This would be a simple script to list the programs which a specific user is executing and then checking all the programs whether they using a specific library: USER="www-data" LIB="libcrypto" while read line; do arr=( $line ) com="${arr[0]}" # only programs with absolute paths (?) if [ "${com:0:1}" != "/" ]; then continue fi ...


0

If you have access to the executables you can use ldd /usr/bin/progname to see what libraries are linked to without requiring any elevated rights.



Top 50 recent answers are included